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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds no behavioral detail beyond the core check, such as whether it returns a boolean, whether it performs any network resolution, or whether a missing deployment is an error. It does not contradict the annotations, so this is a safe but minimal 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?

A single, front-loaded sentence that states the action and object without filler. It is appropriately sized for a simple availability check.

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-required-parameter read-only check, the description is sufficient: an agent can call it to learn whether IntentGuardian is deployed. The phrase 'selected environment' is not defined, but it likely refers to a global context, and the implied boolean outcome is enough given the absence of an output schema.

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 schema has one optional raw 'params' field with no required or typed semantic parameters; schema coverage is effectively complete. The description adds no parameter-specific detail, but none is needed because there are no meaningful inputs to explain.

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 action ('Check') and resource ('environment...IntentGuardian deployment'). It clearly conveys an availability probe and distinguishes it from the peer_guardian_* siblings, which target policy and funding concerns. It does not explicitly name an alternative, so it stops short of 5.

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 guidance on when to use this tool versus any peer_* alternative. The description only states what it checks, leaving the agent to infer from the name and context that it is a preliminary availability probe. No exclusions or routing conditions are provided.

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