Get Lead

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get a single lead by ID' without addressing error handling, not-found behavior, permissions, or response format. This is a minimal disclosure that leaves important operational details unspecified.

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 concise sentence with a documentation link, immediately front-loaded with the action and resource. Every word earns its place, with no redundancy or filler.

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 get operation, the description is adequately complete for an agent to select and invoke the tool correctly. It states the purpose and access method clearly, and the schema covers the parameter. The lack of an output schema and behavioral details is a minor gap, but the tool's simplicity and the provided docs link mitigate this.

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?

The schema already fully describes lead_id as 'Housecall Pro lead ID' with 100% coverage, so the baseline is 3. The description adds no extra meaning beyond 'by ID', leaving the schema to carry the parameter documentation.

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 uses a specific verb 'Get' with a clear resource 'single lead' and access method 'by ID', which clearly distinguishes it from sibling tools like list_leads or create_lead. It is unambiguous about what the tool does.

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 implies usage for fetching a specific lead by its ID, but it does not explicitly state when to prefer this over list_leads or provide any exclusions. No direct comparison with alternatives is given, so the usage context is only implied.

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