fetch_spaces

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

With no annotations, the description only states a read operation but does not disclose pagination, authentication requirements, rate limits, or what 'accessible' means. This is insufficient for an AI agent to understand side effects or constraints.

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 very short and to the point. While it could be slightly more informative (e.g., mentioning it returns a list), it wastes no words and is well-structured for a no-parameter tool.

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 no annotations, the description covers the basic purpose. However, it lacks detail about the return format (e.g., array of space objects) and the meaning of 'accessible', leaving ambiguity for an AI agent.

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 input schema has zero parameters and is fully covered (100%). The description adds no parameter information, but none is required. Baseline score of 3 is appropriate.

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 verb 'Retrieve' and the resource 'all accessible spaces', which distinguishes it from single-space retrieval tools like 'get_space' and other fetch tools by implying a list.

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 is given on when to use this tool versus alternatives such as 'get_space' for a specific space or 'fetch_space_roles' for roles. The context of use is not elaborated.

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