list_confluence_spaces

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

With no annotations, the description carries the full burden. It usefully discloses that results are limited to spaces the user has permission to view and that results can be filtered. However, it does not describe pagination behavior, default result ordering, or what fields are returned for each space, which an agent might need when invoking the tool.

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: one terse sentence for the core behavior and one short sentence for filtering. Every word earns its place, and the key scope (user-visible spaces) is front-loaded.

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 simple list operation with three optional parameters and no output schema, the description is adequate but minimal. It doesn't explain return value structure, pagination beyond the schema's limit parameter, or how this tool relates to nearby siblings like get_confluence_space. Some additional context would improve selection confidence.

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 the schema already explains each parameter, its enum values, default, and limits. The description only adds that filtering by type and status is possible, which is mild extra context but not essential 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 uses a specific verb-resource pair ('Lists all Confluence spaces') and states the permission scope clearly. It is distinct from sibling tools like get_confluence_space, which implies retrieving a single space, though it doesn't explicitly name the alternative.

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 its use when you need a list of accessible Confluence spaces, especially with optional type/status filters. However, it provides no explicit guidance on when to use this tool instead of get_confluence_space or search_confluence_pages, leaving the choice mostly to inference.

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