get_tenant_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'retrieves' information, indicating a read-only operation, and enumerates the returned data. It does not mention authorization requirements or rate limits, but the nature of a read-only configuration tool is adequately transparent.

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 concise, consisting of two sentences. The first sentence front-loads the purpose and scope, while the second provides usage guidance. Every sentence adds value with no wasted words.

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 zero parameters, no output schema, and no annotations, the description fully covers the essential information: what the tool does, what data it returns, and when to use it. It leaves no significant gaps 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 tool has no parameters (0 params, baseline 4). The description does not need to add parameter information beyond the schema, which is already 100% coverage. It appropriately describes what the tool returns without referencing parameters.

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 the tool retrieves 'SAP Datasphere tenant configuration and system information' and lists specific fields like tenant ID, region, version, license type, storage quota/usage, user count, space count, enabled features, and maintenance windows. This verb+resource combination is specific and distinct from sibling tools like get_space_info or get_asset_details, which focus on other scopes.

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 explicitly says 'Use this for system administration and capacity planning,' providing a clear use case. While it does not exclude alternatives or mention when not to use, the context is sufficient for a simple read-only tool with no side effects.

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