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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful scope context (NZX-only, a fixed bundle of report sections, and a PDF alternative at a given path) but says nothing about auth requirements, rate limits, data freshness, or cost of generating a 'comprehensive' report.

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 tool's identity is front-loaded in the first clause and the content list is a single dense sentence with no filler. The trailing PDF-path note is slightly tangential but is genuinely actionable information 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?

With one simple string parameter, full schema documentation, an output schema, and read-only annotations, the description is adequate: an agent knows what it gets back and that the call is safe. The main gap is the absence of routing guidance against near-duplicate board tools, which is a usage-guideline concern rather than a completeness one.

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% and the single ticker parameter is documented with examples ('FPH', 'AIR', 'SPK') directly in the schema. The description adds no syntax, constraint, or format detail beyond that, so the baseline 3 applies.

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 and resource — 'Get a comprehensive Board Gap Intelligence Report for an NZX company' — and enumerates the report's contents (composition, skills gap, director profile, fee benchmarking, governance scores, risk flags). However, it never distinguishes itself from the many similar siblings such as get_board_composition_report, get_board_skills_matrix, get_board_benchmark, or get_board_health_score, which overlap heavily with the listed contents.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite ~20 board-related siblings. The content enumeration weakly implies 'use this when you want everything at once' but the agent must infer that itself.

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