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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a useful breadth list of what the dashboard covers, but does not disclose behavior beyond what the output schema presumably shows (e.g., freshness, aggregation limits, or sourcing).

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?

One densely packed sentence front-loads the purpose and lists components efficiently. Nothing is wasted, though the long em-dash enumeration makes it list-heavy rather than optimally structured.

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 an output schema covering return values and annotations covering the safety profile, the main remaining gap is routing: the description never says when this aggregate view is preferable to the dozen-plus overlapping board siblings. For a broad dashboard tool in a crowded namespace, that omission is a real incompleteness.

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% for the single required ticker parameter, and the schema already documents the NZX ticker format with examples. The description adds no additional meaning about the parameter, so the baseline of 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?

The description states a specific verb+resource ("Get comprehensive board effectiveness dashboard") and enumerates the dashboard's contents (composition, skills heatmap, governance score, benchmarking, succession risk, attendance, remuneration). It is clear what the tool returns, but it never distinguishes itself from the many overlapping siblings (get_board_benchmark, get_board_skills_matrix, get_governance_scorecard, get_succession_plan, get_remuneration_benchmarks), leaving that differentiation to the agent.

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 guidance on when to use this tool versus the numerous alternative board/governance tools. "Comprehensive dashboard" hints at an aggregate overview use case, but no condition selects it over get_board_composition_report, get_board_health_score, or the individual component tools.

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