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

The description adds behavioral context beyond the readOnlyHint and openWorldHint annotations: it requires OAuth or X-API-KEY, costs 2 credits per page, and notes the result is filing evidence, not investment advice. No contradiction with 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?

The description is four sentences long and front-loads the main purpose. Most sentences are informative, though the disclaimer about investment advice is marginally necessary. Overall efficient.

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 no output schema, the description does not detail the structure of returned events (e.g., fields included). It mentions pagination and classification but omits the exact response format. For a tool with 7 parameters, more completeness on output would be helpful.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining concepts like 'inclusive date or timestamp', 'opaque next_cursor', and the 1-50 ticker limit, enhancing clarity beyond the 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 clearly states the tool returns classified executive-compensation disclosure changes for 1-50 tickers since an inclusive date. It specifies what is included (changes, not snapshots or full history) and distinguishes from sibling tools by focusing on material changes.

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 mentions authentication requirements (OAuth or X-API-KEY) and cost (2 credits per page). It also states it does not include current snapshots or full historical rows, providing some guidance when not to use it. However, it does not explicitly compare to sibling tools like get_executive_compensation.

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