list_spaces

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

With no annotations, description carries full burden. It explains what fields are returned (IDs, names, status, counts) and conditionally owner details. It implies read-only behavior but doesn't explicitly state no side effects. Reasonably transparent for a listing tool.

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?

Well-structured with markdown sections, bullet points, and concise sentences. Every section adds value: purpose, usage conditions, output description, example queries, and next steps. No fluff.

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 one optional parameter and no output schema, the description is comprehensive. It covers what to expect in results and suggests follow-up actions. Sibling tools are not needed for completeness of this tool.

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 baseline is 3. Description adds value by explaining the parameter's effect (include_details adds owner, dates, connection counts) and default behavior. Goes beyond schema to clarify practical usage.

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?

Description explicitly states 'List all SAP Datasphere spaces with their status and metadata.' It specifies the resource (spaces), action (list), and output elements (status, metadata). It distinguishes from sibling tools like get_space_info by positioning it as a next step.

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?

Provides clear 'Use this tool when:' section with specific scenarios (e.g., user asks about spaces, starting exploration, checking status). Also includes 'Next steps' suggesting get_space_info for further details. However, does not explicitly state when not to use or compare with other list tools.

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