list_cluster_reports

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

With no annotations provided, the description carries the full burden of behavioral disclosure and delivers almost none of it. It does not state that listing is a read-only, non-mutating operation, says nothing about ordering, default page size, or whether results include reports still queued or running, and gives no return-shape context.

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 front-loaded sentence with no filler or hedging; the purpose is stated immediately. It could have used the remaining space to add one routing or filtering hint, but nothing present is wasted.

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 six-parameter list tool with no output schema and no annotations, the description is thin: it omits pagination behavior, result ordering, and how status or is_detailed filters change the returned set. An agent can technically call it, but several decisions are left entirely to the schema.

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%, so all six parameters (limit, offset, status, is_detailed, target_type, cluster_snapshot_id) are already documented in the schema with enums and bounds. The description adds no filtering semantics beyond the schema, which makes the baseline 3 appropriate.

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 gives a clear verb plus resource: it lists 'generated multi-phase comparative mythology reports and monographs'. This distinguishes it from the singular get_cluster_report, though it never names a sibling to contrast against, so the differentiation is implicit rather than explicit.

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 at all: nothing says when to prefer this over get_cluster_report, list_cluster_snapshots, or list_jobs, and no prerequisites or filter-selection advice is offered. The agent must infer usage from the name alone.

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