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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two real behavioral facts beyond that: values are provider-reported (source trust) and unknown values are preserved rather than dropped or coerced (fidelity). It says nothing about the default 30-day window, caps, or result volume.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is part of why key semantics are missing.

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 no output schema, the description carries the burden of conveying what is returned, and 'features' across five provider categories is too abstract to let an agent predict the response shape. The time-window parameter is also unexplained, so the definition is thin for even a two-parameter read 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 only 50%: workspaceId is documented in the schema, but the 'days' lookback parameter (default 30, range 1-90) has no schema description and is never mentioned in the description. The description therefore does not compensate for the coverage gap on the one parameter that controls result scope.

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 gives a concrete verb ('Read') and enumerates the resource categories (web search, maps, shopping, ads, comparison features), so the agent knows roughly what comes back. However, 'features' itself is never defined, and the description never ties the tool to answers/prompts or a workspace, leaving the object of the read ambiguous.

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 stated preconditions, and no named alternative among the many get_*/list_* siblings. The only usage hint (workspaceId from list_workspaces) comes from the schema, not the description.

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