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

Annotations already cover the safety profile fully (readOnlyHint true, idempotentHint true, destructiveHint false). The description's 'read-only' echoes readOnlyHint and 'No input' restates the empty schema, adding little new behavioral context. It is fully consistent with annotations, so no contradiction penalty applies, but the description contributes minimal behavioral value beyond the structured fields.

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?

Three sentences with no filler. Content scope is front-loaded, followed by the when-to-call guidance and the no-input/read-only constraint. Every sentence 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 no-input, read-only overview tool the description is essentially complete. Since there is no output schema, the description carries the burden of describing the return content, which it does ('what AgentAvow is, which tool to use for what, how to read a verdict, and example scans'). Nothing an agent needs to invoke it successfully is 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?

There are zero parameters and schema description coverage is 100%, so the baseline is 4. The description's 'No input' correctly confirms what the empty schema already shows, and no further parameter documentation is needed.

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 purpose — an overview/help tool covering what AgentAvow is, tool routing, verdict interpretation, and examples. The verb 'Call this for an overview' clarifies its role, and the content list distinguishes it from the sibling scan/verify/check tools, though the differentiation is implicit rather than explicit.

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?

'Call this for an overview or when getting started' gives a clear when-to-use trigger. It doesn't name alternatives or give explicit when-not-to-use conditions, but the contrast with the operational siblings (scan, verify, lookup) makes the intended context reasonably clear.

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