crm_get_lead

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), which is clear, but doesn't mention permissions, rate limits, error handling, or response format. For a tool with 3 parameters and no output schema, this leaves significant behavioral gaps uncovered.

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, efficient sentence that front-loads the core action ('Get a single lead by ID') and adds necessary qualifiers. There is zero waste—every word contributes to understanding the tool's function without redundancy.

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?

Given 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'properties' and 'associations' entail, how results are structured, or behavioral aspects like errors. For a read tool with sibling alternatives, more context is needed to guide effective use.

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 description must compensate. It adds meaning by explaining that 'leadId' retrieves 'a single lead by ID', 'properties' are 'specific properties', and 'associations' are 'associations' (though vague). This clarifies the purpose of parameters beyond the bare schema, but doesn't detail format or constraints (e.g., what properties/associations are available).

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 clearly states the verb ('Get') and resource ('a single lead'), specifying it retrieves by ID with 'specific properties and associations'. It distinguishes from siblings like crm_list_objects or crm_search_leads by focusing on single retrieval, though it doesn't explicitly name alternatives. The purpose is specific but lacks explicit sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives like crm_get_lead_properties or crm_search_leads. It implies usage for retrieving a specific lead by ID but doesn't mention prerequisites, exclusions, or contextual recommendations. No explicit when/when-not statements are present.

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