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

Annotations already establish read-only and non-destructive behavior; the description goes beyond them by disclosing extraction from narrative text, verification before publication, reverse-chronological ordering, and the back-filling coverage caveat with explicit empty-result semantics. This adds real behavioral context without contradicting the 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?

Every sentence earns its place: scope, source, return fields, ordering, extraction/verification behavior, and the coverage/empty-result caveat. The most important scoping information is front-loaded before the detailed behaviors.

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 properly enumerates the returned fields: person name, raw and normalized role, action, effective date, verbatim disclosure, and filing source. Combined with full parameter documentation and safety annotations, nothing needed to invoke the tool 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?

All six parameters are fully documented in the input schema, so the description does not need to add parameter-level meaning. The prose adds useful output and coverage context but does not materially extend the semantics of ticker, date filters, action, offset, or maxResults.

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 precise verb and resource: getting a company's executive and director changes from 8-K Item 5.02 filings. The event types are enumerated, and the source filing basis distinguishes it clearly from siblings such as GetExecutiveCompensation.

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 makes the use case clear: an agent needing executive/board appointment, resignation, termination, or retirement events from a company's 8-K filings. It does not explicitly name alternative tools or exclusion conditions, but the source-specific scope gives clear selection context.

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