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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the response is comprehensive ('everything about one lead'), implying no filtering or pagination, but says nothing about permissions, missing-lead behavior, or result size.

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 front-loaded sentence that lists the payload by category. No filler and no 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?

With no output schema, the description usefully enumerates the returned content categories, which is the main thing an agent needs. It omits any parameter guidance, which is the one remaining gap for a one-argument read 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 0% and the description never mentions the lead_id parameter beyond the phrase 'one lead'. It does not clarify that the argument is a UUID identifier or how to obtain one, leaving the sole required parameter largely undocumented.

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 resource and enumerates its returned contents (contact info, pitch angles, deal details, call history, notes), so an agent knows exactly what it fetches. It does not explicitly contrast with siblings like find_leads or call_history, but the 'one lead' scoping is clear.

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?

Usage is only implied by the purpose: fetch the full profile for a known lead. It never states when to prefer this over find_leads (discovery) or call_history (call-specific view), nor any prerequisite such as needing an existing lead_id.

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