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

The annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond those fields: it is free, requires an API key or connected account, includes private issues, and returns current status for each item.

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 front-loaded and generally readable, but the authentication requirement is stated twice: 'Free; needs a key' and then 'Needs an API key or a connected account.' That duplication and fragmented phrasing reduce efficiency.

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 simple read-only personal list with one optional limit parameter and no output schema, the description covers the key content, status inclusion, cost, authentication, and primary use case. It still omits minor operational details such as pagination or ordering, but is otherwise sufficient.

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 100%, and the single limit parameter is already fully documented in the schema. The description adds no additional meaning about limit behavior, so the baseline score of 3 is appropriate.

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 personal scope: items you filed (including private issues), items you follow through votes/comments, and your review, each with status. It distinguishes a personal list from the sibling list_feedback by emphasizing 'you filed' and 'your review,' though it does not name alternatives explicitly.

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 a clear use case: checking on an issue you reported or a feature you asked for. It does not explain when to prefer get_feedback, list_feedback, or list_reviews instead, so the routing guidance is helpful but incomplete.

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