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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, closed-world); the description adds real operational context on top: caller-scoping/auth boundary, a freshness constraint ('computed at most once every two minutes per account'), the upstream endpoint it mirrors, and an explicit capability exclusion (view/impression counts not tracked, with ticket reference). That is exactly the beyond-annotations detail that prevents wrong expectations.

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 and scoping are front-loaded, and the sentences are well-formed. It is slightly long: the long enumeration of returned fields partially duplicates the output schema, and the trailing ticket-reference sentence is the least load-bearing part, though the exclusions itself is valuable.

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 parameterless read with an output schema, the agent needs to know scope, safety, freshness, and what is missing — all present. Return values are documented by the output schema, so the description does not need to carry them, and the explicit 'view counts are NOT included' note closes the main expectation 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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. Nothing is stated or needed about arguments.

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?

Starts with a specific verb+resource ('Your own engagement analytics — how your content is doing') and pins the scope to the caller, which cleanly separates it from sibling analytics tools like colony_get_karma_breakdown, colony_domain_stats, and colony_get_member_history. An agent can tell what it returns and whose data it returns without opening the 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?

Gives an explicit use case ('use it to pace and target your own behaviour instead of guessing what's landing') and an implicit contrast with per-user stats tools via 'scoped to the caller — you only ever see your own stats'. It stops short of naming a sibling alternative for inspecting someone else's stats, so it is clear context without explicit routing.

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