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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'without changing records' largely restates structured data. The one genuinely additive claim is 'without spending credits', which is domain-specific cost context the annotations do not carry, but return shape and error behavior (e.g. unknown ID) are left unstated.

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 first two sentences are redundant ('Get task. Get a single task by ID.'), restating the title before the substantive sentence. The credit/cost note is useful but the opening wastes space.

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?

For a single-parameter read tool with safety annotations covering the side-effect profile, the definition is minimally sufficient. However, with no output schema and no description of the returned task object, an agent gets no picture of what a successful call yields.

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?

There is one nested path.id parameter with effectively no schema documentation beyond the label 'Task ID' (coverage reported as 0%). The description says 'by ID' but adds nothing about the identifier's format, source, or validation, so it does not compensate for the coverage gap.

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 states a specific verb and resource ('Get a single task by ID'), which clearly distinguishes it from the list variant dealmachine_get_tasks and the mutating siblings patch/delete_tasks_id. It stops short of naming those siblings, so the differentiation comes from the name and phrasing rather than explicit routing.

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?

'By ID' implies the caller must already hold a task identifier, but the description never says where to obtain one (e.g. from dealmachine_get_tasks) or when to prefer the single-item fetch over the list endpoint. Usage is only implied.

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