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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the notion of 'deterministic signed assessment' hinting at signature generation but provides no detail on what is signed, what the output contains, or any side effects. This is minimal extra context beyond the annotations.

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?

The description is extremely short (one sentence) but it is under-specified rather than concise. It fails to convey essential information, making it ineffective. The brevity is not beneficial because it sacrifices clarity; it does not 'earn its place' by providing any actionable detail.

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 tool with three required parameters and a rich set of siblings, this description is wholly inadequate. It does not explain what the assessment does, what the parameters mean, or what the output schema provides. Even with annotations and an output schema, an agent cannot determine when to call this tool or what inputs to supply. The description is far from complete.

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 description coverage is reported at 100%, implying each parameter (catalog, ttl_ms, cache_scope) has a description in the actual schema. Since the schema already documents these, the description need not repeat them. However, the description adds no additional semantic nuance beyond 'over supplied input', so it earns the baseline 3.

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 'deterministic signed assessment over supplied input' which gives a vague sense of purpose (assessment) but does not specify the resource, action, or scope. It fails to differentiate from numerous sibling tools with similar names like 'cache' related or 'guard' tools, and the purpose is ambiguous. It is not a tautology but is far from clear.

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 absolutely no guidance on when to use this tool versus any of the many siblings. No context, no alternatives, no conditions for invocation. The description is silent on usage scenarios entirely.

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