view_lead

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

No annotations are provided, so the description carries the full behavioral burden and contributes almost nothing: 'view' weakly implies a read-only operation, but there is no statement about permissions needed, whether the lead must be owned by the caller, or what happens with an invalid ID. For a tool with zero annotation coverage this is a notable gap, though low risk since it is a retrieval.

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 short sentence, front-loaded with the verb and resource, with no filler or redundancy. Its brevity borders on under-specification, but nothing in it is wasted.

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 lookup this is roughly adequate, and with no output schema it need not enumerate return values. Still, it never characterizes the response ('detailed information' is vague) or clarifies its relationship to search_leads/list_leads, leaving room for the agent to pick the wrong retrieval tool.

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%, so lead_id ('Lead ID') is already documented, and the description adds no format, range, or sourcing detail beyond it. With the schema doing all the work, the baseline of 3 is appropriate.

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 gives a specific verb ('View') and resource ('a lead') with a scope qualifier ('detailed information'), so the agent knows it is a single-record fetch rather than a list. It does not, however, distinguish itself from the nearby siblings list_leads, search_leads, or update_lead, which share the same resource.

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 guidance on when to choose this over search_leads or list_leads, nor any stated prerequisite such as already holding a lead_id. The single required parameter implies a lookup-by-ID use case, but that inference is left entirely to the agent.

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