get_directors

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

No annotations are provided, so the description must disclose behavior. It only states returns name, roles, appointment dates, but does not mention read-only nature, auth needs, or pagination. The implicit 'List' suggests a safe read, but fails to provide explicit transparency.

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?

Two sentences, 18 words, immediately states purpose and usage. Every sentence adds value. No fluff.

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?

Description covers search and company filter but omits mention of limit and current params. Since there's no output schema, the description should at least list returned fields (which it does for name, roles, appointment dates) but it fails to inform about pagination or boolean filter. Incomplete.

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 has 100% coverage with detailed descriptions. The description adds usage context for search and company params, but does not reveal new constraints or types beyond what schema provides. Baseline 3 is appropriate.

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 'List directors of NZX-listed companies' with a specific verb and resource. It differentiates from sibling tools like get_director (single director) and get_company_directorships (directorships by company).

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 usage by listing search and filter options, but does not provide explicit guidance on when to choose this tool over siblings like get_director or get_company_directorships. No exclusions or alternatives are mentioned.

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