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

Annotations already establish readOnly, idempotent, and non-destructive. The description adds the two facts annotations cannot express: the call is free (no credit spend) and it never triggers work. Per-channel scope is also disclosed. Return shape is left to the output schema, which exists.

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?

Three short sentences, front-loaded with the returned data set, then cost/side-effect, then the usage trigger. Every clause carries information an agent needs.

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?

Purpose, cost, side-effect profile, and call ordering are all covered, and return values are handled by the output schema. The only material gap is the undocumented brandId parameter.

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?

The single parameter brandId has 0% schema description coverage, and the description never explains what it is or how it scopes the result beyond the vague phrase 'for every connected channel.' With coverage this low the description is required to compensate and does not.

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 ('Check') and enumerates the exact resource set it returns: reporting support, saved X reports, credit prices, refresh permission. Ambiguity against siblings like request_x_report is eliminated by the explicit 'never starts work' qualifier.

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?

'Read this before requesting fresh reports' is an explicit when-to-use rule that routes the agent to this tool ahead of the request_* siblings. No exclusion or prerequisite is left to inference.

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