pmu_verify

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

The description discloses the dossier-freshness gate and repo auto-location, adding behavioral context beyond the schema. However, it does not describe the output format, side effects, or success/failure behavior.

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 a dense paragraph containing necessary information but is not well-structured. Some jargon and parenthetical details reduce readability.

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?

The description covers the tool's operation and extra gates, but lacks output information. Given no output schema and no annotations, it is moderately complete for a two-parameter tool.

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 description adds meaningful context to both parameters: explaining when repo_root is needed and that skip_build sets an environment variable. This goes beyond the schema descriptions.

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 clearly states the tool's purpose: reproducing PMU due-diligence claims by running a script. It uses specific verbs and resources, but the domain jargon may slightly obscure the purpose for an AI agent unfamiliar with the terms.

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 explicit guidance on when to use this tool versus siblings. The description details operational aspects but does not mention alternatives or exclusions.

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