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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds useful return-content detail (score, evidence quote, reason, stage, link) that matters because there is no output schema, though it does not discuss authorization or not-found 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 a single front-loaded sentence with no filler, and each clause lists a distinct piece of returned data. It is appropriately sized for a simple single-record read tool.

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 low-complexity read operation, the description covers what the tool does and what fields it returns, while annotations cover the safety profile. The missing parameter semantics and lack of error or not-found behavior keep it from being fully complete.

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 0%, so the schema itself provides no descriptions for projectId or leadId. The description never mentions either parameter, leaving their meaning to be inferred from conventional names; this is a clear gap despite the names being relatively intuitive.

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 opens with a specific verb-resource pair ('Read one lead') and scopes it to a single record, clearly separating it from list_leads, get_leads_overview, and move_lead_stage. It also names the main returned fields, so the tool's purpose 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?

It implies usage when a single lead is needed, but does not explicitly say when to choose it over list_leads, get_leads_overview, or move_lead_stage. No prerequisites or exclusions are stated, leaving usage guidance only implied.

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