Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the transparency burden. It reveals the permission requirement and a key error outcome (404), which helps the agent anticipate results. It does not mention that no data is modified, but the verb 'Reads' implies read-only behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, direct, and free of extraneous detail. Every sentence contributes meaningful information about the action, permission, or error behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers permission and error cases but does not describe the response shape or the fields that will be returned for the task. Since there is no output schema, this is a notable gap for an agent that may need to consume the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions are just the parameter names, adding no semantics. The description adds context that the task belongs to a tenant CRM and that organization_id scopes the read, but it does not explain ID formats, relationships, or expected values beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Reads one task') and the resource ('tenant CRM'), distinguishing it from plural fetch, create, update, and delete siblings. No ambiguity about the tool's core purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides actionable guidance by mentioning the required permission (crm:read) and the 404 behavior for foreign or missing IDs. It does not explicitly name an alternative for listing multiple tasks, but the singular 'one task' implicitly directs usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.