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

The description adds non-obvious behavioral details: 'Group pages do not limit counts' clarifies pagination semantics, and 'multi-asset groups overlap' explains overlapping group membership. It also explicitly states that no sentiment or performance score is inferred, which prevents misinterpretation. Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with these.

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 description is three terse sentences with no fluff. The primary action and grouping options are front-loaded, followed by two crucial behavioral notes. Every sentence earns its place, making it highly efficient for an agent to parse.

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?

Despite having 16 parameters and no output schema, the description does not explain the return format, pagination behavior beyond the group-page note, or any filter semantics. It covers the core purpose but leaves agents without crucial details on how to construct queries or interpret results, making it incomplete for a tool of this complexity.

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?

With 44% schema description coverage, the description carries only minimal parameter meaning. It mentions grouping by day, author, or asset, which maps to the group_by enum, and clarifies multi-asset overlap, but it does not explain filters like chain_ids, asset_type, evidence_class, or exclude_post_types. The description adds little beyond the schema for most of the 16 parameters.

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 clearly states the tool counts filtered posts and groups them by day, author, or asset, with a specific verb and resource. It distinguishes itself from retrieval tools like get_posts by emphasizing aggregation, but it does not explicitly name alternatives or contrast with similar aggregation tools like compare_activity or get_engagement_history.

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?

No explicit guidance is given on when to use this tool versus siblings. The description implies it is for counting/aggregation, but it never states conditions, exclusions, or mentions alternatives such as get_posts for raw data or compare_activity for comparative analysis. An agent would have to infer usage from the tool name and schema.

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