get_spaces

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

With no annotations provided, the description carries the full burden. It only says 'list all available', but does not disclose pagination behavior, rate limits, or what 'available' means (e.g., excludes archived spaces). No behavioral traits beyond the bare operation are disclosed.

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 a single sentence, which is concise but at the expense of completeness. It could include more detail without becoming verbose, so it is adequate but not maximally effective.

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 no annotations, output schema, or sibling context in the description, the tool is under-documented. It lacks details about space ordering, filtering, or response structure, making it less complete than expected for a list-all operation.

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?

The schema coverage is 100% with one parameter 'limit'. The description adds the default value (50) not present in the schema, providing useful context. However, it does not elaborate on the parameter's effect beyond the schema's description.

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 'List all available Confluence spaces' clearly states the verb 'list' and the resource 'spaces', making the tool's purpose unambiguous. It differentiates from sibling tools like get_page (single page) and search_pages (search) by focusing on listing all spaces.

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 provides no guidance on when to use this tool versus alternatives, such as search_pages or get_page. It merely states the listing action without context on limitations or prerequisites.

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