get_tenant_info

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

With no annotations, the description carries the full burden. It describes what is retrieved but does not explicitly state safety traits like read-only behavior, permission requirements, rate limits, or any side effects. The verb 'Retrieve' implies a read operation, but the description adds no deeper behavioral disclosure.

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 a single well-structured sentence that front-loads the primary purpose, then enumerates key fields and ends with a usage note. Every phrase earns its place, with no redundant or filler content.

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 parameterless read tool with no output schema, the description is quite complete: it lists the returned data types (tenant ID, region, version, etc.) and the use case. It does not mention error cases, authentication needs, or response format, but the level of detail is adequate for a simple retrieval 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?

The input schema is empty (0 parameters), so the baseline is 4. The description correctly implies that no parameters are needed, and there is nothing more to explain about parameter semantics.

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 retrieves SAP Datasphere tenant configuration and system information, listing specific fields. It uses a specific verb ('Retrieve') and resource ('tenant configuration'), but does not explicitly distinguish from sibling tools like get_space_info or get_current_user, though the tenant-level scope is implicit.

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?

It explicitly says 'Use this for system administration and capacity planning,' providing clear context for when to use it. However, it does not mention when not to use it or name alternative tools, so it lacks exclusions/alternatives.

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