repo_intel

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

No annotations are provided, so the description carries the burden. It does indicate a read-only verification action and that it returns a status verdict plus alternatives, but it does not disclose potential side effects, network behavior, rate-limit implications, or error conditions. This is adequate but not rich.

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 short, focused, and front-loaded with the core purpose. Every sentence contributes value: what it verifies, what it returns, and when to use it. No redundant or filler content.

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?

Given the sibling tools (find_repos, health) and the explicit note that the repo is 'already found,' the description is contextually complete for typical use. It could provide more detail about the output shape, but it covers the essential need: verifying a repo before dependency commitment.

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 already provides descriptions for owner_repo, query, and top_k, including an example for owner_repo. The description adds context by mentioning 'best-of-kind' and 'a few alternatives,' which aligns with query and top_k behavior, but it does not explicitly map each parameter.

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 ('Verify') and identifies the resource (an existing repo the agent already found) and the key checks (alive, licensed, best-of-kind). It clearly distinguishes this from the sibling tools by emphasizing it is not for discovery, making the purpose unambiguous.

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?

It explicitly states when to use the tool: 'BEFORE committing to a dependency to catch archived/stale/no-license repos.' This gives direct, actionable guidance and implicitly contrasts with the find_repos and health sibling tools.

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