repo_overview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context with 'fast' and 'evidence-only,' signaling low latency and that results are raw findings rather than inference or recommendations — but it says nothing about output format, cost, or whether it scans the working tree versus the index.

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?

One tightly written sentence with the core action front-loaded and no filler. It is dense with enumerated scope, which is efficient, though the list-of-nouns style slightly blurs what each item actually reports.

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, the description must convey what comes back, and it does so only via an enumeration of inventory categories. Combined with the missing path-format guidance and lack of sibling differentiation, the definition is adequate but leaves an agent guessing about return structure and where this fits in a workflow.

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?

There is one required parameter, repo_path, with 0% schema description coverage, so the description carries the full burden — and it says nothing about expected format (absolute vs relative path, root vs subdirectory) or behavior for an invalid path. A single-sentence mention of path semantics would have closed this gap.

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 ('Gather') and resource ('repository shape') and enumerates the inventory dimensions (languages, tests, index freshness, deployment artifacts). This clearly differentiates it from single-dimension siblings like language_profile or software_inventory, though it never names an alternative directly.

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?

The description gives no when-to-use guidance and never contrasts itself with the many overlapping siblings (language_profile, software_inventory, production_readiness, diagnostics). An agent must infer that this is the broad first-pass reconnaissance tool rather than a focused analyzer.

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