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 covered. The description adds meaningful scope context beyond the annotations: the analysis is restricted to NZX and to current chairs, plus it enumerates the three output components (chair list, interlock pairs, network metrics).

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 purpose, then return contents, then usage triggers in a logical order. The metric enumeration is slightly list-heavy but every clause carries useful information, so it is close to optimally sized.

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 present, the description need not explain return values, yet it does so helpfully. Combined with annotations covering the safety profile, an agent has enough to call this correctly; the only minor gap is the absence of an explicit alternative tool for director-level networks.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. No misleading parameter claims are made.

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 (Analyze) and a precisely scoped resource (the NZX board chair interlock network), and clarifies the unit of analysis is chairs with multiple board seats. This is distinguishable from adjacent siblings like get_director_network and get_network_intelligence, which cover directors or generic networks rather than chair interlocks.

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?

Explicit trigger phrases ('chair networks, board interlocks among chairs, serial chairs, or how NZX board chairs are connected') tell the agent exactly when this tool applies. It does not, however, name the closest alternative (e.g., get_director_network) and state when to prefer that one instead, so the routing guidance is one-sided.

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