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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions pagination, which is useful, but it does not clarify whether it requires specific permissions, the scope of changes (e.g., covering only certain companies), or the meaning of the 'days' parameter (lookback window). It also leaves the return format unspecified further.

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 extremely brief (essentially one sentence plus a single word 'Paginated.'), which is concise and front-loaded. It wastes no words, but could add minimal value without bloating, so it earns a high score for conciseness.

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 complexity of 5 parameters, 0% schema coverage, and no output schema, the description is far from complete. It does not explain pagination behavior (e.g., page size limits), how to handle type_key, or what the response contains. An agent would have to guess or infer many details.

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 0%, so the description must compensate. However, it only explains pagination and mentions the 'days' parameter implicitly (from the schema) but does not elaborate on what 'days' controls or the meaning of 'type_key'. The schema itself provides defaults but no descriptions, so the agent lacks clarity on each parameter's purpose.

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 it lists director appointment/resignation/role changes, which is specific (verb 'list' + resource 'director changes'). It is likely distinct from sibling get_director_roster, which probably returns the current roster rather than changes, so it helps differentiate.

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 implicitly suggests it is for fetching a list of director changes (with pagination) but does not explicitly state when to use it versus siblings like get_director_roster or get_corporate_actions. No exclusions or alternatives are named, leaving the agent to infer context.

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