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

With no annotations, the description carries the behavioral burden. It discloses that this is a read-only personal summary and names the specific aggregates surfaced, but it does not mention data freshness, time range, output format, or whether results are live or cached. The description is helpful but not deeply transparent.

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 compact and front-loads the essential value proposition and specific metrics. The middle sentence, 'Turns your input into visible collaboration,' is somewhat promotional and does not add operational information, but the overall structure is efficient.

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 zero-parameter, no-output-schema tool, the description provides enough information for an agent to understand what the call returns and why it matters. The main missing context is explicit relationship to sibling tools and any caveats about scope or data timing.

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 has zero parameters, so the baseline per rubric is 4. The description adds relevant scoping context ('Token-scoped to you') that clarifies the implicit parameter space even though the schema is empty.

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 uses a specific verb ('See') and a specific resource ('your feedback + pattern requests ... shaped the shared library'), and enumerates the concrete metrics returned: verdicts rated, patterns requested, and patterns approved. This clearly distinguishes it from siblings like my_usage or what_others_did.

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 description implies the tool is for viewing one's own contribution summary, but it never explicitly states when to choose it over alternatives such as my_usage (likely token/usage stats) or what_others_did (others' activity). No when-not-to-use or alternative-routing guidance is provided.

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