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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value that the annotations do not carry: the cost of $0.008 USDC on Base and that output is token-optimized clean Markdown. It still says nothing about how payment is executed, latency, rate limits, or failure modes, which matter for a paid open-world call.

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 sentence, but the front-loaded portion is pricing and marketing jargon rather than the core capability. Words like 'High-velocity Agent Operational Primitive' consume prime position without adding decision-relevant information. Reordering so the action and output lead would make it much stronger.

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?

With only two simple parameters and no output schema, the description covers cost and output format, which is helpful. However, it omits what a returned block contains (source URLs, citation metadata) and how the limit shapes results, leaving the agent guessing at result structure. Adequate but with clear gaps for a paid external-call tool.

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 100%, so both query and limit are already documented in structured form. The description adds no syntax, format, or semantics for either parameter and does not clarify what a 'grounded block' is. Baseline 3 applies because the schema does the work.

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 names a concrete action and output: real-time web grounding plus clean Markdown synthesis, explicitly stripped of HTML, ads, and scripts. This separates it from knowledge-base or registry lookups among the siblings. It loses a point because the leading phrase 'High-velocity Agent Operational Primitive' is marketing framing rather than a clearer statement of purpose.

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 explicit when-to-use, when-not-to-use, or named alternative (e.g. vault_knowledge_search for internal docs). The only usage signal is an implied one: 'for LLM context windows' suggests it is for grounding prompts. An agent must infer everything about routing and prerequisites, including how payment and auth are expected to work.

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