direct.hf.pressure_report

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'read-only' merely repeats that. The useful addition is 'best effort', which signals results may be incomplete or approximate, a behavioral trait not covered by annotations, but nothing is said about auth/account resolution, rate limits, or cost.

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 a single front-loaded sentence with no filler, and the scoping caveat ('best effort') is stated compactly. The 'Human-friendly:' prefix is borderline fluff but does signal the output style, so the sentence is efficient overall.

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 13-parameter report tool with semantic-cluster inputs, the description never explains what 'market pressure' measures, how clusters shape the report, or what the output schema contains conceptually. Even with an output schema covering return fields, the agent lacks the conceptual grounding needed to use this tool correctly alongside its many report siblings.

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 every parameter (date_from, date_to, clusters, account_id, etc.) is already documented in the schema. The description adds no syntax, format, or default details beyond what the schema provides, so the baseline of 3 is appropriate.

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 it produces a 'market pressure report by semantic clusters', which names a resource and clustering dimension, but 'market pressure' is undefined jargon and the verb is only implied. It does not differentiate itself from sibling report tools like direct.hf.report_performance or direct.hf.report_search_phrases, so an agent cannot confidently tell when this report is the right one.

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 when-not-to-use guidance, and no named alternative among the many direct.hf report siblings. The only routing hint is the 'semantic clusters' phrase, which is left for the agent to infer.

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