get_lead

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

No annotations are provided, but the description only states what is retrieved and adds no detail about errors, missing IDs, authentication, or output shape. 'Get' weakly implies read-only, but the description does not substantiate that behavioral profile.

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?

One short, front-loaded sentence conveys the tool's core purpose with no filler. Under-specification is a completeness concern, not a conciseness one.

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 one-parameter getter this is enough to invoke correctly, but with no output schema and no annotations it omits expected return shape and not-found behavior. A brief note about what the tool returns or errors on would make it 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?

With one parameter and 0% schema description coverage, the description should carry more of the semantic burden. It ties lead_id to the lookup via 'by id', adding minimal meaning beyond the parameter name and type.

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 ('Get'), resource ('lead'), and selection criterion ('by id'). It is immediately distinct from sibling tools like list_leads or search_leads_by_email.

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?

The phrase 'by id' implies this tool is for retrieving a single lead when the caller already has the lead_id. No explicit comparison to alternatives like list_leads or search_leads_by_email is provided, so usage guidance is left to inference.

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