list_environments

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

With no annotations, the description carries the full burden, and 'No SAP call' is a genuinely useful disclosure: the tool makes no remote SAP request, so there is no auth requirement or latency concern. That said, it says nothing about whether the result is cached or how login status is determined, and the safety profile must be inferred.

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?

Three short fragments with zero filler, and the resource is named first. It is telegraphic to the point of reading like a caption rather than a description, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and with no parameters the calling contract is trivial. Still, for a discovery tool that gates all other SAP operations, the absence of any guidance about when to invoke it leaves a meaningful gap.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline is 4 for a no-argument tool; the description does not complicate or misrepresent the calling contract.

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 names the resource (SAP systems/environments) and specifies exactly what is reported: availability, which one is active, and login status. It omits an explicit verb like 'list', but the content is specific enough that an agent can distinguish this from switch_environment and sap_login, which act on a single environment rather than enumerating them.

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?

There is no statement of when to call this versus siblings such as switch_environment, whoami, or list_services. The phrase 'No SAP call' hints that it is a cheap local check, but the description never tells the agent to use it before initiating SAP operations or to discover valid environment names.

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