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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the optional filter only changes the display (opens a tree on that initiative) while the full list is still returned, which is non-obvious and useful. It omits auth/visibility scoping details and pagination, keeping it short of a 5.

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 purpose, then routing guidance and parameter guidance in a logical order. Slightly redundant: 'the full list is still returned' appears twice (once in prose, once restated), which costs a little efficiency but does not obscure the message.

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 explanation is unnecessary. For a single optional-parameter, read-only list tool the description covers purpose, routing, nesting behavior, and the filter's display effect — nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the parameter's own description already covers case-insensitive partial matching and the tree display. The description reinforces the intent (use it when asked about work beneath an initiative) but adds little syntactic meaning 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 (List) and resource (initiatives visible to this person in Genchi) plus the payload (anonymous confidence signal per initiative). It also clarifies nesting semantics via the 'Part of' column, which separates it from write-oriented siblings like genchi_create_initiative.

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?

Gives explicit trigger phrases ('what am I tracking', 'how are my projects doing') and names the exact condition for using the optional parameter ('what's happening under the platform programme', 'break down Infrastructure Modernisation'). An agent knows both when to call it and when to pass initiative_name.

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