list

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the useful return-scope rule (whole root unless `collection` is given), but says nothing about pagination, result ordering, or volume, which matters for an unbounded 'list'.

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?

A single tight sentence with the scope rule front-loaded ahead of the filtering note. Efficient, though the parenthetical is slightly dense given how little it actually specifies.

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?

For a 6-parameter, zero-required, zero-coverage tool with no output schema, the description is too thin — an agent cannot tell what the filters mean, what the default return shape is, or how results are bounded.

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 0% across 6 parameters, so the description carries the full burden and largely fails: only `collection` is named, and 'optionally filtered' vaguely gestures at tag/type/owner/ready/status without explaining what values they accept or how they combine.

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 ('List initiatives') and clarifies the scope boundary (whole root unless `collection` is given), which compensates for the bare tool name 'list'. It does not differentiate itself from siblings like `collections`, `get`, or `ready`, which could also surface initiative-like data.

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 when-to-use guidance relative to the many sibling tools; 'optionally filtered' hints that filters exist but never says when to prefer this over `collections` or `get`. Only the `collection` scoping rule is stated, and that is behavioral rather than usage selection.

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