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

Annotations already declare readOnly=true, destructive=false and closed-world, so the safety profile is covered. The description adds only 'date filtering', saying nothing about pagination behavior (skip is a page number, not an offset), the 100-item limit cap, or the admin/owner restriction on owned_by that are material to calling it correctly.

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?

A single low-waste sentence with the resource front-loaded after the name restatement. The brevity is not the problem; the sentence simply carries little information.

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 and the input schema is fully described, so return values and parameters need not be explained. However, for a six-parameter reporting tool surrounded by overlapping analytics siblings, the description leaves the core question — what data this returns and how it differs — unanswered.

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 100%, so all six parameters are already documented, including the skip-as-page-number conversion and the limit maximum. The description contributes only a generic reference to date filtering, adding no syntax or semantics beyond the schema.

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 verb+resource ('retrieve activity reports') and a scope hint ('date filtering'), but 'activity reports' is vague next to siblings like get_analytics_daily, get_analytics_overall, get_clicks_activity and get_sent_activity. An agent cannot tell from the description whether this returns report objects, analytics aggregates, or activity logs.

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?

There is no when-to-use guidance and no mention of any alternative. Among a dozen report-adjacent siblings, nothing indicates why or when an agent should pick this tool over get_analytics_* or get_*_activity.

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