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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety and repeat-call profile is fully covered structurally. The description adds only the fact that it targets a previously submitted request (implying existence/lookup semantics), with no note on error behavior for unknown IDs or rate limits.

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?

A single tight sentence with the resource front-loaded before the key parameter. It is appropriately sized, though it is arguably slightly under-informative rather than wasteful.

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?

With an output schema present, return values need not be explained, and this is a trivial one-parameter read. The main residual gap is not telling the agent what a returned 'status' can be or what to do if the lead_id is unknown.

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?

Schema description coverage is 100% and the single lead_id parameter is documented as the ID returned by request_home_service. The description adds no format, validation, or lookup semantics beyond that, so the schema carries the entire burden and the baseline of 3 applies.

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 ('Look up a previously submitted service request by lead_id'), which is clearer than the tool name's vague 'lead status'. It does not, however, explicitly differentiate itself from the similar sibling get_plumbing_call_number, so it stops short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as the other lookup/status siblings. The only implicit signal is the schema note tying lead_id to request_home_service, which the agent must infer applies to usage.

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