get_space_info

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

No annotations are provided, so the description carries full burden. It discloses output contents (metadata, tables/views, schemas, row counts, connection info) and error behavior (if space not found, list_spaces() shows available spaces). It does not explicitly state read-only nature, but the wording strongly implies it.

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 (purpose, when to use, what you'll get, parameter, examples, errors). It is slightly verbose but every section adds practical context. Slight redundancy with the parameter requirement already in schema, so not perfect.

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, the description compensates with a detailed list of returned data types. It covers purpose, usage, expected output, parameter specifics, and error handling. Missing only minor details like performance implications, but is sufficient for correct invocation.

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% and already documents space_id with UPPERCASE requirement and examples. The description repeats this without adding new semantic meaning, so it meets the baseline but does not go beyond.

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 opens with a specific verb and resource: 'Get comprehensive information about a specific SAP Datasphere space.' It clearly lists what is included (metadata, tables/views, schemas, row counts, connection info) and implicitly distinguishes from sibling tools like list_spaces by focusing on 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?

Includes a dedicated 'Use this tool when' section with concrete triggers (user asks about a specific space, need to see tables/views, checking configuration). It explicitly mentions following up from list_spaces() results and suggests list_spaces as an alternative when space is not found.

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