list_review_reports

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

With no annotations, the description is the only behavioral signal. It does disclose that the operation is local and that it only surfaces previously generated reports, implying no new generation or remote scanning. It does not, however, describe result ordering, empty-state behavior, or whether the operation is purely read-only, which would be helpful without annotations.

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 a single, tight sentence with no filler. Every word contributes meaning: 'previously generated,' 'stored locally,' and 'reports' all constrain the tool's behavior.

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 list tool with one optional parameter and no output schema, the description covers the essential context: what is listed, where it comes from, and that it is limited to prior local report generation. Additional return-format details would be nice but are not critical for correct invocation.

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 schema has one optional 'limit' parameter with default, minimum, and maximum, but no additional description coverage. The parameter name plus constraints make its meaning reasonably clear, so the description does not need to restate it. Still, the description adds no value about how 'limit' affects the returned list.

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 ('List') and names a precise resource ('previously generated GitLumen MCP reports stored locally'). This clearly separates it from siblings like get_review_report (fetching one report) and screen_repository (scanning a repository), so an agent can identify its role immediately.

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 wording implies the tool is for enumerating already-generated local reports, which hints that it would be used before get_review_report. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions, leaving some routing to inference.

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