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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so safety is covered structurally. The description adds genuine behavior — result ordering (newest first), grouping by concept, inclusion of AI-assisted and 'checked' work — but leaves undefined jargon ('commons', 'checked') and says nothing about result limits or pagination.

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 short sentences with no filler, and the default-handle instruction is placed where an agent will read it before constructing arguments. The first sentence is slightly denser than needed ('added to the commons and checked'), but nothing is wasted.

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 one-optional-parameter read tool with annotations covering safety, the definition is nearly sufficient, but with no output schema the agent gets no sense of the return shape — a list of entries, counts, or per-concept groups — nor of pagination or 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 0% (the single `handle` property has no description, only a pattern), so the description must carry the burden — and it does, explaining both that the handle identifies 'a person' and that omitting it defaults to the signed-in user's own contributions. That is a meaningful semantic gain beyond the bare string pattern.

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 concrete resource — what a person (and their AI) contributed and had checked — plus an ordering rule (by concept, newest first). It does not name a distinguishing sibling (concept_activity, search), so an agent must infer the boundary, but the resource itself is unambiguous.

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?

The only procedural guidance is parameter-oriented: omit the handle to get the signed-in person's own contributions. There is no explicit when-to-use-this-vs-alternative guidance, e.g. versus concept_activity or search, so usage is implied rather than stated.

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