confluence_list_spaces

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

No annotations provided, so description bears full burden. It mentions 'accessible to the authenticated user,' implying authentication, but says nothing about pagination, rate limits, or behavior when no spaces exist. Minimal transparency for a read-only list 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?

Extremely concise: one sentence with no wasted words. However, lacks structure like bullet points or sections. Slightly improved would be adding a line about usage notes.

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?

Given the tool's simplicity (one optional param, no output schema), the description is fairly complete: it says what it does, scope (accessible spaces), and implies it's a list operation. Could mention ordering or defaults, but acceptable.

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 coverage is 100% (only 'limit' param described). The description adds no extra meaning beyond the schema's 'Max number of spaces to return.' Baseline 3 applies.

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 all Confluence spaces accessible to the authenticated user.' It uses a specific verb ('list') and resource ('spaces'), and distinguishes from sibling tools like get_space (single space) and list_pages_in_space (pages within a space).

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 vs alternatives. It does not mention when to prefer this over get_space or get_space_by_key, nor any exclusions or prerequisites.

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