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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context about what the response contains (proficiency per director, gap analysis, diversity score) and framework alignment, but does not note data sources, staleness, or coverage limits. Adequate but not rich beyond 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?

Front-loaded with the core action in the first sentence, followed by the content breakdown and framework note. The 12-category list is somewhat enumeration-heavy but conveys concrete output value rather than padding.

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?

Output schema exists, so return values needn't be explained, and annotations cover the safety profile. However, given the dense set of adjacent board tools, the description omits the differentiation and scope boundaries an agent needs to select it correctly.

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 description coverage is 100%; the single ticker parameter is fully documented with examples ('FPH', 'AIR', 'MEL'). The description adds no further parameter meaning, so the baseline 3 is correct.

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?

Clear specific verb+resource ('Get board skills matrix for an NZX company') and it enumerates the exact output content (12 skill categories, proficiency levels, gap analysis, diversity score). It does not differentiate itself from closely related siblings such as get_board_gap_report, get_board_effectiveness, or get_board_benchmark, so an agent can identify the tool but not easily pick it over neighbors.

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?

No statement of when to use this tool versus the many overlapping board-analysis siblings, and no exclusions or prerequisites. Usage is only implied by the verb 'Get', which is insufficient against a sibling set packed with board_* tools.

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