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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond them: the seven-day default window and the hard 31-day ceiling, which tell the agent how far back it can reach without extra calls.

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?

Two tight sentences: the first defines what the feed contains, the second gives the default and the limit. Nothing is repeated and the content definition is 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?

With one optional parameter, full schema coverage, no output schema and strong annotations, the description supplies what an agent needs to call it correctly. It could go slightly further by hinting at the shape of the per-day records, but that is a minor gap.

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 100% and the schema already documents 'days' with minimum 1 and maximum 31. The description's main addition is the undocumented default of seven days, which is mildly useful, but the 31-day cap simply restates the schema's maximum.

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?

The description names the concrete resource (a per-day activity feed) and enumerates the record types returned: posts, pages, replies, emails. An agent can distinguish it from siblings like whats_happening or hosted_pages, though it never uses an explicit verb such as 'list' or 'retrieve'.

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?

Usage is only implied: an agent must infer this is the tool for reviewing recent output volume. There is no explicit when-to-use or when-not-to-use guidance, and no sibling (e.g. whats_happening, approvals_waiting) is named as an alternative.

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