confluence_get_spaces

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description need not reiterate. The description adds no additional behavioral context, such as pagination behavior or authentication needs. A 3 is appropriate as annotations cover the base safety profile.

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 of 4 words, which is under-specified. It omits critical context like pagination and return format, making it too concise to be fully useful.

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 output schema and pagination parameters, the description should explain what the tool returns and how pagination works. It fails to do so. The sibling context is rich, but the description does not help the agent differentiate.

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%; both 'limit' and 'start' have descriptions in the schema. The tool description adds no further parameter information. Baseline 3 is correct.

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 the tool lists spaces, using a specific verb and resource. It distinguishes from sibling tools like 'confluence_get_space' and 'confluence_get_space_by_key' which target individual spaces. However, the phrasing 'List all spaces' is slightly misleading due to pagination limits.

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. It does not mention that for a single space, 'confluence_get_space' or 'confluence_get_space_by_key' should be used. No prerequisites or context are provided.

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