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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds real value beyond them: the shape of the returned report, the mandate to display formattedText verbatim, and the empty-state procedure (direct the user to open Analytics in the app). It stops short of describing pagination, size, or freshness of the report, and gives no guidance on whether the returned text may be edited or truncated.

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?

Purpose is front-loaded in the first sentence, and the following sections are scannable labeled blocks rather than prose. The all-caps IMPORTANT instruction earns its emphasis because it changes how the agent renders output, though the definition is slightly longer than strictly necessary for a one-parameter read tool.

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 simple read-only tool with no output schema, the definition covers what the report contains, how to render it, when to prefer the sibling, and what to do when no overview exists. The only real gap is the absence of any detail on report volume or ordering, which is minor given the single optional 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?

There is a single optional parameter, social_set, and schema description coverage is 100%, so the schema already explains that it accepts a name, id, or handle and that it should be omitted when the user has only one set. The description adds nothing further about the parameter, so the baseline 3 applies.

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 ("Load the user's overview report from SupaBird Analytics") and enumerates the report's contents (high/low engagement insights, examples, tweet cards). It explicitly contrasts with the daily report sibling, so an agent can distinguish the two without opening either schema.

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?

Provides an explicit "When to call" block covering the user intents that select this tool (overview, account review, what content works) and names an alternative with its selecting condition: a specific calendar day goes to get_daily_performance_report. Nothing 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.