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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: newest-first ordering, the three activity categories included, and that both human and AI actors are attributed. It does not mention any result cap or pagination beyond the days window.

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 tightly written sentences: the first front-loads what is returned and its ordering, the second covers the use cases. No filler and nothing repeated from the annotations or schema.

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 only two parameters, no output schema, and no nested objects, the description does the work of describing the return contents and ordering, which is exactly what is needed for a read-only feed. The remaining gap is the undocumented concept identifier format and any result-size limits.

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 50%: 'days' is documented in the schema (default 7, max 90) and 'concept' has only a pattern with no prose. The description implies scoping to one concept but adds no format or identity guidance for the required concept parameter, so it does not fully compensate for the gap.

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 resource and result shape: recent work on a concept, newest first, covering tasks taken, versions added, and checks made, with actor and AI attribution. It is clearly a per-concept activity feed, though it never names or contrasts the closest siblings (e.g. contributions, list_tasks) to make the boundary explicit.

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 two concrete use cases: checking whether someone is already working on the concept, and following up on activity your own work triggered. There is no when-not guidance and no named alternative tool, which keeps it below a 5.

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