get_environment_capabilities

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

Annotations already declare readOnlyHint=true, so the bar is lower, and the description still adds real value: it discloses that results are separated into metadata evidence versus untested permissions and SDK support, and that the connection and API version are left untouched. The only gap is that it does not describe the shape of the returned payload, and there is no output schema to fall back on.

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?

Two sentences, zero waste, front-loaded with the operation and its constituent reads, followed by the interpretive caveat and the side-effect exclusion. Every clause carries information the agent needs.

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 zero-parameter read-only tool with no output schema, the definition covers what is read, how evidence should be weighted, and what side effects do not occur. The remaining gap is the return structure, which the agent must discover by calling, but that is a minor omission given the tool's simplicity.

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 and the schema is an empty object, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly avoids inventing parameter behavior.

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 states a specific verb ('inspect') and resource ('the configured CRM environment') and names the concrete sub-reads (WhoAmI, RetrieveVersion, table definitions), so the agent knows exactly what it will get. It stops short of explicitly contrasting with overlapping siblings such as get_current_user_context or list_all_entity_definitions, so differentiation 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?

Usage is implied by the framing ('inspect the configured CRM environment') and by the exclusions ('does not change the connection or select another API version'), which help the agent avoid expecting mutation. However, no sibling is named and no explicit when-to-use/when-not-to-use rule is given, leaving the agent to infer this is a diagnostic discovery call.

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