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 fully covered structurally. The description adds scope value by disclosing that this is a composite briefing spanning eight analysis areas, but it says nothing about breadth cost, data freshness, or how the sections are assembled.

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 core purpose before the content list. The enumeration is long but each item earns its place by defining the briefing's scope; a slight trim of the list is possible without losing meaning.

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-value structure need not be explained, and annotations carry the safety profile. The description is adequate for an agent to know what the tool returns and when it is broadly relevant, with only the usage-routing detail left implicit.

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?

There is one parameter with 100% schema coverage, and the schema already documents ticker as an NZX ticker symbol. The description adds no format, constraint, or example detail beyond the schema, 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 (get) and resource (board meeting preparation briefing) and enumerates the component analyses it bundles (governance scores, insider activity, dividend analysis, financial health, AGM status, board changes). This distinguishes it as an aggregate/multi-section briefing rather than a single-metric sibling like get_board_composition_report. It stops short of explicitly naming the alternative tools it supersedes.

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 phrase 'board meeting preparation briefing' implies the intended use case, but there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as get_ir_briefing or get_board_health_score. Usage is only inferable from the name and the enumerated content.

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