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

Discloses multi-source fan-out, GDELT→GNews fallback, USPTO soft-fail due to API sunset, accepted date formats, and return structure. Annotations already indicate safety, but description adds meaningful behavioral context beyond annotations.

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?

Front-loaded with examples, informative but slightly verbose. Every sentence earns its place, though minor tightening possible. No waste, but length could be reduced slightly without losing clarity.

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?

Despite no output schema, description fully explains return format (changes[], total_changes, citation URIs). Covers all necessary details for a tool with 3 required params and no nested objects.

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%, yet description adds value: clarifies 'type' only supports 'company', gives examples for 'value' (ticker or CIK), and recommends '30d' or '1m' for 'since'. Enhances usability beyond schema alone.

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 explicitly states 'change feed for a company in the last N days/weeks/months in ONE parallel call,' supported by concrete example queries like 'What's new with X.' It distinguishes from sibling tool entity_profile by specifying when to use each.

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?

Provides clear when-to-use guidance with example queries and explicitly directs to use entity_profile for static profiles, offering an alternative in a separate sentence.

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