List Confluence Spaces

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the tool returns key and name and supports filters, but it doesn't disclose extra behavioral traits like pagination behavior or response structure beyond what the schema/annotations imply.

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?

The description is extremely concise and front-loaded: 'Get spaces. Returns key and name. Filter by space_key, status, label, favourite.' Every sentence adds value without waste.

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 7-parameter tool, the description covers purpose, return fields, and key filters, but omits guidance on pagination parameters (limit, start) and doesn't clarify valid status values. The output schema exists, so return values are presumably structured, but the description alone is not fully complete.

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 only 14% (only save_path has a schema description). The tool description names four filters (space_key, status, label, favourite) but doesn't explain their value formats or semantics (e.g., valid status values, boolean usage for favourite). It adds little over the schema's type definitions.

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 the action ('Get spaces') and the resource (Confluence spaces), and notes the return fields (key and name). However, it does not explicitly distinguish this from sibling tools like search or get_content_by_id, though the resource is distinct.

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 usage by listing available filters (space_key, status, label, favourite), giving context for when to call it. It lacks explicit guidance on when not to use it or when to prefer alternatives such as search, so it falls short of a 4.

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