fetch_pdb

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

Annotations already declare openWorldHint=true, idempotent=true, destructive=false, so the network-write profile is partly covered. The description adds real value on top: the source servers (BORER_SYMBOL_SERVER or Microsoft's), the https transport, the GUID/age validation gate, and the dry-run default. It does not cover failure modes (GUID mismatch, download errors) or cache location, so not a 5.

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 sentences, no filler. The core action and cache rule come first, the when-to-use and workflow follow, and the dry-run constraint is placed where an agent needs it before invoking.

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?

For a one-parameter, no-output-schema tool with helpful annotations, this covers what it does, when to call it, and what to do afterward. Minor gaps remain around what happens on GUID mismatch or download failure, but nothing essential to a correct call is missing.

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?

With 100% schema coverage on the single parameter, the schema already explains dry_run's default and effect. The description only reinforces the default with 'dry run until dry_run=false', which is procedural rather than new semantic detail, so baseline 3 applies.

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: downloads the missing PDB for the loaded PE, over https, into the cache. It also states the retention rule (kept only if GUID and age match), which separates it clearly from siblings like load_binary and symbols.

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?

Explicit trigger: 'Use it when load_binary reports no PDB'. Explicit sequence: dry run first, set dry_run=false, then re-run load_binary. Both the when and the surrounding workflow are named with a sibling tool.

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