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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; openWorldHint=false also sets scope. The description adds that data is limited to the person's own published posts and to a bounded recent window, but it omits the 90-day ceiling on the window and any statement about aggregation or freshness.

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?

One front-loaded sentence that states the subject, the metrics, the scope and the default window with no filler.

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 one optional parameter, read-only annotations and no output schema, the description covers what an agent needs to invoke it and know what it reports. Only minor gaps remain (parameter bounds, aggregation semantics).

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%, so the description must carry meaning — and it does supply the key value the schema lacks: the default of 30 days and the semantic of 'last N days'. It does not note the 1–90 bounds, so it only partially compensates.

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?

Names a specific verb (Report) and resource (the person's published social posts' performance), and enumerates the metrics returned (likes, replies, reposts, engagement) plus per-platform granularity. No sibling tool overlaps this role, so an agent can select it without ambiguity.

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?

The time-window phrasing ('over the last N days (default 30)') implies the usage context, but there is no explicit when-to-use/when-not guidance and no named alternative among the many post-related siblings. Adequate but with clear gaps.

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