diagnose

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

Describes the tool as read-only, which is important behavioral info. However, no annotations are provided, so the description carries full burden. It does not detail potential impacts, rate limits, or prerequisites beyond being read-only.

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, front-loaded with the action and return value. No extraneous information.

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 simple diagnostic tool with one optional parameter, the description covers purpose, use case, and return structure (status per check, detail, suggested actions). No gaps.

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 only parameter 'profile' is fully documented in the input schema. The description reiterates that it uses the 'configured qontoctl profile', adding no new semantics beyond the schema. Baseline of 3 is appropriate since schema coverage is 100%.

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?

Clearly states the action: run a read-only healthcheck against a profile, and returns a diagnostic report. It is distinct from all sibling tools which are about accounts, transactions, etc.

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?

Explicitly says 'Use this first when something doesn't work', providing clear when-to-use guidance. Lacks explicit when-not-to-use, but context implies it's for initial troubleshooting.

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