list_react_repos

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does state the return content (names, descriptions, React status), which is helpful, but it doesn't disclose how the 'configured GitHub account' is determined, whether this makes network calls that could be slow/fail, whether results are paginated, or any idempotency/caching behavior. For a tool that appears to be a read-only listing operation, some behavioral transparency is missing.

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 sentences, no filler, front-loaded with the core purpose immediately. Each sentence earns its place: the first states the function, the second states what's returned. It could arguably add usage guidance, but as written it's compact and free of waste. Loses one point for being slightly under-specified rather than elegantly concise.

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 listing tool with only one param, high schema coverage, no output schema, and no annotations, the description is adequate but thin. It doesn't explain pagination, ordering, error behavior, or how the 'configured' account is established, and with no output schema the agent has to infer the return structure from the prose. Given the tool's apparent simplicity (list repos), a 2 reflects that it meets minimum expectations but doesn't fully equip the agent.

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 100% and there's only one parameter (includeNonReact), which the schema already describes as 'Include non-React repositories in the listing.' The description's phrase 'from the configured GitHub account' adds context about the source scope, and the parameter is straightforward. Since schema fully covers the param, baseline is 3, but the description's mention of the configured-account source adds marginal value relevant to the listing scope, justifying a 4.

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+resource combination ('List all React repositories') that clearly states the tool's function. It names what it returns (repo names, descriptions, React status), distinguishing it from siblings. However, it doesn't explicitly contrast with sibling tools like get_repo_structure or validate_all_repos, so it loses a point for sibling differentiation.

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?

No usage context is provided. There's no guidance on when to use this tool vs alternatives, no prerequisites mentioned (e.g., needing a configured account already in place), and no exclusions stated. The context signals show no annotations to help, and the description gives only an implicit 'use this to list React repos' which is self-evident.

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