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 only the word 'deterministic' and 'signed', which hints at output behavior but does not explain what 'signed' means or what the assessment entails. No contradictions with annotations, but minimal added value.

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 only one sentence, but it is unhelpfully vague and lacks front-loaded, actionable information. It does not earn its place because it merely restates the tool's name and adds an opaque phrase.

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?

Despite having an output schema, the description fails to explain the input, the meaning of the assessment, or the expected result. For a tool with a single required parameter and a clear purpose implied by its name, this is severely under-specified.

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 required parameter 'quote' but no description for it. The tool description does not elaborate on what constitutes a 'quote' or how it should be formatted. With zero schema descriptions and no tool-level explanation, an agent cannot correctly construct the input.

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 'deterministic signed assessment over supplied input' is vague and doesn't clearly state what the tool does. It echoes the title without clarifying that it assesses the freshness of a quote. It doesn't distinguish it from sibling tools like data_freshness_certificate or live_data_freshness, leaving an agent unable to determine its unique function.

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 alternative. No context is provided about typical scenarios, prerequisites, or exclusions. The agent has no basis to decide between this and the many freshness-related sibling tools.

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