list_spaces

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

Annotations are absent, so the description carries the full burden. It discloses what the tool returns (space IDs, names, status, counts, owner with include_details=True) and implies a read-only operation via 'list.' However, it does not explicitly state permissions, pagination, or potential errors, which would be even more transparent. The default behavior and detail flag are explained, earning a 4.

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 well-structured with clear sections and is front-loaded with the main purpose. Some content, like example queries, is slightly redundant but still useful for intent recognition. It is not overly verbose, so 4 is appropriate.

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 simple read-only list tool with one optional parameter and no output schema, the description thoroughly covers use cases, expected outputs, parameter semantics, and next steps. It is fully complete for an agent to understand when and how to invoke it.

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%, so the schema already documents include_details well. The description adds minor context by mentioning 'quick space listing' vs. detailed information, but largely duplicates the schema's parameter description. Thus it meets the baseline without significant added meaning.

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 it lists all SAP Datasphere spaces with their status and metadata. It distinguishes itself from siblings by mentioning it's for discovering spaces, while get_space_info is for exploring a specific space and search_tables is for finding tables. This provides a specific verb-resource pair with scope.

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 explicit 'Use this tool when' bullets, example queries, and next steps that point to alternatives like get_space_info and search_tables. This constitutes clear usage context and alternative guidance, satisfying the highest bar.

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