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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds useful context about ordering (reverse-chronological) and the types of events included, which goes beyond the annotations and provides behavioral insight without contradiction.

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, front-loaded sentence that states the verb, resource, and content scope with zero waste. It is efficient and immediately informative.

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 the presence of an output schema (not shown but declared), the description need not explain return values. The tool is simple with one parameter, and the description covers purpose, scope, and ordering. Nothing essential for an agent to call it correctly is missing.

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 for the single parameter deal_id. It adds the semantic constraint that the deal must be 'known' (i.e., already exist), which is not in the schema and helps the agent understand it cannot be used to create a deal. This is valuable, though it doesn't elaborate on format or retrieval.

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 ('Inspect') and identifies the exact resource: a single deal's reverse-chronological timeline of Data Parrot AI assessments, CRM changes, and customer engagements. This clearly distinguishes it from siblings like get_deal (basic deal info) or get_engagements (only engagements) by naming the composite content.

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 use when you have a known deal_id and want its full timeline, but it does not explicitly mention alternatives or state when not to use it. The purpose is clear enough that an agent could infer context, but there is no explicit routing guidance among the many sibling tools.

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