get_space_info

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

No annotations provided, but description clearly implies a read-only operation ('Get comprehensive information') and lists what will be returned. It adds context like uppercase requirement for space_id. Could be more explicit about being read-only or lack of side effects.

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 sections for usage, output, parameters, examples, and error handling. Every sentence is meaningful and adds value. No unnecessary text.

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 tool with one parameter and no output schema, the description covers all necessary aspects: purpose, when to use, parameter details, example queries, and error handling. It is complete.

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 schema already documents the parameter. Description adds value by specifying the uppercase requirement and providing example queries, though it largely restates the schema description.

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 explicitly states 'Get comprehensive information about a specific SAP Datasphere space' and lists specific outputs (metadata, tables/views, schemas). It clearly distinguishes from siblings like list_spaces by specifying it targets a single space.

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 explicit 'Use this tool when:' section with concrete scenarios (user asks about a space, need to see tables/views, follow-up from list_spaces). Also gives error handling guidance (if space not found, use list_spaces).

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