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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the data is the 'latest' snapshot and volumes are 'provider estimates,' which tells the agent how much to trust the numbers. It does not, however, describe return format or pagination.

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?

Two tight sentences with the core content (what is searched, volumes, change) front-loaded and no wasted words. The provenance caveat is correctly appended rather than leading.

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 single-parameter, annotation-covered read tool with no output schema, the description is adequate about content but incomplete on routing: in a crowded read_* namespace it does not tell the agent when to pick this over read_search_intelligence or read_search_dataset.

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?

With schema coverage at 0%, the description must compensate for the sole parameter, project_id, but it never mentions it or explains the required project scoping. The agent gets no semantic help beyond the raw uuid type in the schema.

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 clear verb+resource combination: it returns search demand for a market, including volumes and change over time. It is concrete about content, but among a large set of sibling read_* tools (read_search_intelligence, read_search_dataset, read_query_evidence), it never distinguishes itself from those alternatives.

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. Usage is only loosely implied by the phrase 'in this market,' leaving the agent to guess how this differs from the other read_* demand/query tools.

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