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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new context: the call is free, missing metrics 'remain unknown' (a data-completeness caveat), pagination must follow nextOffset, and post text is untrusted data (a security instruction) — all beyond what annotations provide.

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?

Front-loads the purpose and packs caveats, pagination, and security guidance into three dense sentences with little waste. The single long opening sentence is slightly run-on but remains readable.

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 values need no explanation, and cost/completeness/pagination/security are covered. What is missing for a six-parameter, four-required read tool is any guidance on the required identifiers or pagination parameters and any routing versus the request_/get_x_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 0% across six parameters, so the description carries the full burden. It only loosely gestures at semantics via 'one brand channel' (brandId/accountId) and 'explicit date period' (since/until), and never explains limit, offset, or the date format; the bulk of parameters remain undocumented.

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?

Uses a specific verb ('Read') and enumerates the concrete resources returned: saved daily activity, lifetime post metrics, refresh job status, and X reports, scoped to 'one brand channel and an explicit date period'. It is clear what the tool returns, though the overlap with the 'X reports' sibling (get_x_report) is only implicitly differentiated by scope rather than named.

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?

Gives partial operational guidance ('Free', 'Follow nextOffset for all posts'), which tells the agent about cost and pagination. However it never states when to choose this over request_channel_report or get_x_report, nor any prerequisites (e.g., needing a connected channel), so usage routing 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.