Find candidate repositories

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

Annotations already declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so safety is mostly covered (though 'Retrieve' sits oddly against readOnlyHint=false). The description does add non-obvious behavior: results carry ranking instructions the agent is expected to act on, and long output is chunked ('Long results come in parts'). It omits what the ranking instructions look like, whether calls are cached/idempotent, and how parts relate to each other.

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 short sentences, front-loaded with the purpose before the output caveat; nothing is wasted. It is arguably too terse for a four-parameter, paginated tool, which costs it the top score.

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?

With no output schema and a tool whose whole purpose is producing a ranked, paginated result set, the description should explain what 'ranking instructions' are, how parts are exhausted, and how pool and top interact. None of that is present, leaving the agent to discover the return contract by trial.

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 all four parameters (top, part, pool, language) are already documented in the schema; baseline is 3. The description adds only marginal meaning, mainly the pagination hint tied to 'part'. It never explains the pool-vs-top relationship or what 'language for the explanations' produces.

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 a specific verb and resource: 'Retrieve candidate GitHub repositories for the profile', plus what comes back ('with ranking instructions'). It is clear what the tool does, but it never differentiates itself from siblings such as search_repos or check_repo, so the agent must infer which retrieval path applies.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named despite seven siblings including search_repos and get_evidence. The only contextual cue is the vague 'for the profile', which does not tell an agent at what point in the workflow this call belongs.

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