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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that the payload concerns budget consumption and check counts, which the output schema already defines, so it contributes little beyond structured data but contradicts nothing.

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?

It is a single short fragment with no wasted words, but it is under-specified rather than concise, lacking a verb or lead-in. There is no structure guiding the agent to usage or parameters.

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?

Because an output schema exists, the description need not enumerate return fields, yet it does so while omitting purpose, usage, and parameter meaning. For a status lookup sitting beside list_covenants, grant_covenant, and revoke_covenant, that leaves the essential selection information missing.

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 description coverage is 0% and the sole required parameter, covenant_id, is never mentioned in the description. The agent gets no hint about identifier format, whether it accepts a name or UUID, or what happens with an unknown value.

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 is a noun phrase listing the data fields returned ('current state, consumed/remaining budget, and check count') rather than stating a verb and resource. An agent can infer it reads the status of a single covenant from the name, but nothing distinguishes it from list_covenants, which likely reports similar per-covenant figures.

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 when-to-use guidance, no mention of alternatives such as list_covenants, and no prerequisites. The agent must infer that a known covenant_id and a need for a single covenant's budget snapshot select this tool.

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