verify_artifacts

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

No annotations are provided, so the description must carry full behavioral disclosure. It does not explain what 'verify' means (e.g., integrity, authenticity, policy checks), nor does it describe failure behavior, output format, or any side effects. This leaves significant ambiguity for a batch-verification tool.

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?

Three concise sentences: the first states the core function, the second gives concrete use cases, and the third provides an explicit alternative. No filler or redundancy; every sentence earns its place.

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 purpose and usage well, but lacks key context: there is no output schema, and the description does not disclose what the response contains (e.g., per-artifact results, pass/fail summary). The undocumented 'policy' parameter also leaves gaps. It is adequate for basic selection but not fully complete for invoking correctly.

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 50%: the 'artifacts' parameter has a description, but 'policy' does not. The tool description adds no information about the 'policy' parameter or its relationship to verification. The agent is left guessing what policy values are valid or required, despite the description mentioning use cases.

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') with a concrete resource ('many artifacts') and explicitly contrasts with the singular sibling tool ('verify_artifact'). The phrase 'Verify many artifacts in a single call' clearly communicates what the tool does and differentiates it from similar tools.

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 explicit use cases: 'checking a dependency list, a lockfile, or several candidate packages at once.' It also provides a direct alternative by stating it is 'preferred over calling verify_artifact repeatedly,' which helps the agent choose between siblings.

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