list_tasks

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

Discloses 'Atomic snapshot under the registry's lock so the result is internally consistent' and describes return shape. With no annotations, this adds meaningful behavioral context, though it could mention that it's read-only.

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 convey purpose, filters, behavioral guarantee, and return shape. No unnecessary words.

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?

No output schema, but description explains return counts and task records. Covers key aspects for a list tool, though the return shape depends on poll_task's documentation.

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?

Input schema provides full parameter descriptions (100% coverage). Description only reiterates 'optional status / type filters and a limit' without adding new meaning beyond the schema.

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 clearly states 'Enumerate all tasks in the FUCMCPTaskRegistry' with optional filters and limit. This distinguishes it from sibling tools like poll_task (single task retrieval) and cancel_task (mutation).

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 description implies listing tasks but does not explicitly state when to use this vs poll_task or other siblings. No exclusions or alternative guidance is provided.

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