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

Annotations already declare readOnly/idempotent/openWorld and non-destructive, so the safety profile is covered. The description adds useful information those annotations lack: results arrive one page at a time. It says nothing about ordering, default page size, or how cursor ties to limit.

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 clause packs scope, pagination and both filters with no waste. The parenthetical '(q)' is slightly awkward but earns its place by mapping the terse param name to 'search words'.

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?

Adequate for a simple read-only list tool whose annotations already cover safety, but with zero schema description coverage the description should pin down the org identifier format, default limit, and cursor semantics. Those gaps could cause malformed calls.

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 0%, so the description must carry the load. It explains three of the five params conceptually (team, q as search words, pagination), but org (ID vs slug?) and the limit/cursor pairing remain undefined.

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?

States the resource (repos) and scope (the org's repos) with pagination as the delivery mode, so an agent knows exactly what is returned. It doesn't explicitly distinguish itself from repo_search or source_repos, which is the only shortfall.

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?

Implies usage — use it to browse an org's repos and narrow with team or q — but never states when to prefer this over repo_search or source_repos, nor when the filters are required versus optional.

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