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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely new behavioral fact — no human confirmation is required — plus an enumeration of the data surfaced, which tells the agent what it gets back in the absence of an output schema. It stops short of describing return shape or size.

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?

One front-loaded sentence opens with the core purpose, then lists returned data, then closes with the key behavioral caveat. No filler. The trailing 'This call asks no human' is terse to the point of being cryptic, but it earns its place.

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 read-only inspection tool with three simple flat parameters and no output schema, the enumeration of returned data does useful work in place of a return spec. Still missing is scope clarification: which environment is inspected, whether results default to a single environment, and how it differs from service_status.

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 67%, and the required 'service' parameter has no description at all. The description never mentions any parameter, so it does nothing to compensate — notably it never clarifies whether project/environment are needed to disambiguate which Service (and which environment's staged state) is inspected.

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 a specific resource ('one Service') and enumerates exactly what it returns: settings with values and defaults, variables, mounts, Configs, domains with status, and staged state. That is far more concrete than a name restatement. It does not, however, distinguish itself from the neighboring service_status or service_logs, so an agent must infer the boundary.

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?

'This call asks no human' implies it is safe to invoke autonomously without confirmation, which is implied usage guidance. But there is no explicit when-to-use statement, no mention of when service_status or service_logs would be preferable, and no note on prerequisites such as project/environment context.

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