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

Goes well beyond the readOnly/idempotent annotations by disclosing that the call is free, that it never refreshes, that missing metrics mean unknown rather than zero, and that post text is untrusted data and must not be treated as instructions. The prompt-injection warning and the missing-metrics semantics are exactly the kind of behavioral context an agent cannot get from structured fields.

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?

Four terse clauses, zero filler, each carrying distinct information (scope, cache behavior, data semantics, security). The most decision-relevant facts are front-loaded.

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?

An output schema exists, so return-value documentation is not required, and annotations plus the behavioral notes cover safety and caching. The only meaningful gap is explicit guidance on how this relates to request_x_report. Nearly complete for a single-parameter read.

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 coverage is 0% and the single required brandId parameter is never mentioned in the description, so no meaning (source, format expectations, or how to obtain the id) is added beyond the bare pattern in the schema. With one undocumented parameter and no compensating text, this falls below the baseline.

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?

States a specific verb and resource (Read saved X public reports) and additionally enumerates the bundled return data: request status, credit price, workspace balance. It is distinguishable from sibling request_x_report by the 'saved'/'never refreshes' framing, though it does not name that sibling directly. The bundling of account-status data alongside reports makes the purpose slightly diffuse but still clear.

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?

Implicit rather than explicit: 'Free: never refreshes' hints that this is a cached read and that fresh data requires the request_x_report sibling, but the alternative is never named and no when-to-use/when-not conditions are spelled out. Adequate but leaves the routing decision to inference.

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