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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the auth requirement ('Needs the user's Cotlet API key with access to this app') and the intended workflow. Return contents are listed, partly compensating for the absent output schema.

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 field list is stated twice nearly verbatim ('name, phone, email, status, assigned agent, comments, source and properties toured' then repeated), which is pure redundancy and bloats an otherwise short description. The purpose and the usage/handoff sentences are otherwise well front-loaded.

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-object read tool with full schema coverage and annotations covering the safety profile, this is close to complete: it names the fields returned (useful given no output schema) and states the auth requirement. Only the duplicated field list and lack of explicit alternative reference keep it from being fully rounded.

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 coverage is 100% for the single lead_id parameter, and the schema already says 'Lead ID from list_leads.' The description adds no syntax, format, or sourcing detail beyond that, so the baseline 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?

States a specific verb and resource ('Returns one lead from its detail page'), which clearly differentiates it from the sibling list_leads. The field list also tells the agent what a lead contains. It stops short of explicit sibling naming, but the singular 'one lead' framing is enough to distinguish it.

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?

Gives a concrete scenario: 'Use it to check a prospect before you approve a Safe Mode visit,' which ties the read to a downstream decision. There is no explicit when-not or named alternative, but the guidance is clear about context.

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