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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds significant behavioral context by listing the extensive data returned (profile, pipeline stage, custom fields, saved messages, conversation summaries, tasks, LinkedIn interactions, stage history). No contradictions; it complements the annotations well.

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 consists of two sentences. The first sentence lists the fetched data in a run-on but comprehensive manner; the second provides a strong usage guideline. It is front-loaded and efficient, though the list could be slightly better structured for readability.

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 tool with 2 parameters, 100% schema coverage, and annotations, the description covers the purpose and output categories adequately despite lacking an output schema. It includes usage context and lists the types of data returned, making it fairly complete for an agent to understand what to expect.

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 coverage is 100%, with both parameters already described. The description adds practical meaning by implicitly using contact_id and mentioning 'recent conversation summaries' corresponding to notes_limit. It goes beyond the schema by providing usage context for the parameters.

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 tool fetches 'full CRM context for a lead' and enumerates specific data types (profile, pipeline stage, custom fields, messages, etc.), using the specific verb 'Fetch' and resource 'lead context'. It distinguishes from siblings by recommending it as a first step for personalized outreach.

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 explicitly says 'Call this first for highly personalized outreach,' providing clear when-to-use guidance. It implies that the tool should be used before writing pitches or follow-ups, though it does not list alternative tools specifically. The context is sufficient for an agent to decide when to invoke it.

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