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

Annotations already declare the safe read-only/idempotent profile, but the description adds substantial non-obvious context: activity is 'observations, not intent scores or verified identities,' 'three devices do not establish three people,' the evidence level (none/thin/usable) must be read before concluding, and WeChat names are never exposed (row number is the only identifier). This is exactly the interpretive and privacy context the schema cannot convey.

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?

The text is long and splits into two loosely related blocks, with an extended subscriber-listing section appended after the engagement summary. The subscriber detail (grouping, reachability states, identifier rules) reads like a second tool's documentation and is not front-loaded, so several sentences do not earn their place in this tool's description.

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 two-parameter read tool with no output schema, the description supplies strong interpretive caveats and privacy rules, which is valuable. But it omits any explanation of the required proposal_id, gives no sense of return shape, and conflates the engagement and subscriber functions, leaving gaps for an agent to fill.

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 only 50%: 'days' documents its default but 'proposal_id' has no description at all. The description never explains what proposal_id is or what the days window scopes, so it fails to compensate for the uncovered parameter.

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 states a specific verb and resource: it reads recent device activity (pages reached/skipped, time, downloads, demos, comments, forwarding) and also lists page subscribers. The dual scope (engagement + subscriber listing) muddies the single purpose a bit, and it never contrasts itself against nearby siblings like get_session_timeline or get_downloads, so it falls short of a 5.

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?

It gives explicit routing for a related task ('To remove someone or revoke a code, use remove_subscriber / revoke_subscribe_code on set_publish_notify'), which is genuine when-to-use guidance. However, it offers no guidance on when to call this tool versus the many overlapping read siblings (get_session_timeline, get_downloads, get_folder_analytics), so the core selection decision is left implicit.

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