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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds scope context ('all current directors') and enumerates the credential categories, which is useful, but says nothing about permissions, rate limits, or data freshness beyond that.

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, front-loaded with the purpose, and the exhaustive parenthetical lists of degrees and designations are informative. Slight redundancy between the first sentence's 'qualifications, credentials, universities' and the second sentence's enumeration, but no genuine waste.

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?

An output schema exists, so return values need not be explained, and the single required parameter is fully documented by the schema. For a read-only, one-param lookup the description is nearly complete; the only gap is the absence of sibling disambiguation against closely overlapping board/director tools.

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% and the single ticker parameter is documented with examples ('FPH', 'AIR', 'SPK') in the schema itself. The description adds nothing about parameter format or constraints, so the baseline 3 applies when the schema does all the work.

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 specific verb (Get) and resource (board credentials) and enumerates the concrete content: degrees, professional designations, governance certifications, university backgrounds, and credential gaps. An agent can tell what data comes back, but the description never distinguishes this from overlapping siblings such as get_iod_designations or get_board_skills_matrix.

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?

There is no when-to-use guidance, no when-not-to-use, and no named alternative. The only implicit signal is that it applies to 'an NZX company,' leaving the agent to infer on its own whether to call this versus get_iod_designations, get_director_demographics, or get_board_skills_matrix.

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