List Spaces

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description discloses pagination parameters (cursor, limit) and sort, which is some behavioral context, but does not describe the return format or any default behavior like whether archived spaces are included.

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 compact: a one-line purpose followed by a bullet-style arg list. No redundant text, front-loaded purpose.

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 list tool with 8 optional parameters and no output schema, the description thoroughly covers parameter semantics but omits the return shape/pagination metadata. Given the tool's complexity, this is a minor but notable gap.

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 this description is the sole source for parameter meaning. It explains all 8 parameters with concrete examples for sort, allowed values for type and status, and clarifies comma-separated formats for ids/keys/labels.

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 opens with 'List Confluence spaces', clearly stating the verb (List) and resource (Confluence spaces). This distinguishes it from sibling tools like get_space, list_pages, or list_blogposts.

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 states its function but does not explicitly guide when to use it over alternatives like get_space. The context implies it is for bulk listing with filters, but no exclusions or when-not-to-use guidance is provided.

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