trawl_list_repos

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

With no annotations at all, the description carries the full behavioral burden but supplies almost nothing: no statement that it is a read-only operation, no pagination or result-cap behavior, no behavior on an unknown pool (empty list vs error). Only the word 'indexed' hints that results are limited to already-ingested repos.

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?

A single front-loaded sentence with no filler. It is efficient, though efficiency here reflects under-specification rather than disciplined editing.

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-parameter listing tool with no annotations and no output schema, the description should say what a returned repo entry looks like (name? owner? URL?) and whether results are bounded. Neither is covered, so an agent knows the intent but not the shape of the result.

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% so the baseline is 3, but the schema text itself is only 'Pool name', and the description's 'for a client' actively muddies the meaning of pool_name rather than clarifying it. No explanation of where a pool name comes from or how it relates to clients.

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 verb+resource ('List GitHub repos indexed') is concrete, but 'for a client' introduces a term that matches neither the parameter (pool_name) nor any sibling tool vocabulary, leaving the scoping ambiguous. It also does not distinguish itself from nearby siblings such as trawl_list_sources, trawl_list_pools, or trawl_search_repo.

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?

There is no guidance on when to use this versus trawl_search_repo (search within a repo) or trawl_list_sources (list sources). No prerequisites, no exclusions, no indication of what a caller should do after listing.

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