confluence_list_spaces

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

No annotations provided, so the description carries full burden. It does not explicitly state that the operation is read-only or what permissions are needed. The verb 'list' suggests read-only but lacks explicit disclosure. Basic behavioral context is present but not thorough.

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 relatively short and uses a clear list format. However, it could be more concise by merging parameter details into a single line. It is not overly verbose, but front-loading is minimal.

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 is provided, and the description does not mention the return value or format. A listing tool should clarify what is returned (e.g., list of space objects). The cursor parameter hints at pagination, but pagination behavior is not explained. Incomplete for a read tool.

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 0%, so the description compensates fully by detailing all 4 parameters: limit (default 25, max 250), type (global/personal with default empty), status (current/archived), and cursor (pagination). This adds significant meaning beyond the schema's raw JSON.

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 'List Confluence spaces' with a specific verb and resource. It distinguishes from sibling tools like 'confluence_search_pages' by focusing on spaces, but does not explicitly differentiate from similar listing tools (e.g., 'list_pages').

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?

No guidance on when to use this tool versus alternatives like 'confluence_search_pages' or 'confluence_list_pages'. The context is implied but not explicit, leaving the agent to infer usage.

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