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

With no annotations, the description must carry the behavioral load, and it does disclose one meaningful trait: contacts are returned conditionally based on what the caller is permitted to see. It says nothing about behavior for a missing/invalid lead id, error modes, or whether the response is a single object, leaving real gaps for a read tool with zero annotation coverage.

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 compact sentence that front-loads the returned fields with no filler. It reads as a noun phrase rather than a sentence, which costs a bit of clarity but wastes nothing.

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 simple one-parameter read with no output schema, the description usefully enumerates the returned fields (text, contacts, source, budget) and flags the permission-conditional field. Only error/not-found behavior and permission prerequisites are left uncovered.

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 id parameter is documented as coming from search_leads, so the description need not repeat it. The description adds no format or constraint details beyond the schema, which is the expected baseline for a fully documented one-parameter schema.

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 names the resource (one lead) and enumerates the returned content — full text, contacts, source, budget — so an agent can tell it apart from the list-oriented search_leads sibling. It lacks an explicit verb, but the retrieval intent is unambiguous.

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 statement of when to use this tool versus search_leads or get_market_analytics, and no prerequisites are given. The only workflow hint ("Lead id from search_leads") lives in the schema, not the description, so the description itself offers no routing guidance.

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