resolve_cdn_cem

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

With no annotations, description clearly states that by default server state is NOT modified (register:false) and explains registration behavior. Discloses caching locally. Could elaborate on idempotency or error handling, but covers key behavioral aspects.

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 sentences, no waste. Front-loaded with core action, then usage context, then behavioral detail. 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?

Covers main functionality and usage but omits return value/output description. With no output schema, the agent is left guessing what the tool returns. Also missing error handling notes. Adequate but incomplete.

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 has 100% coverage, but description adds value: explains default behavior for register, fallback logic for cemPath, and purpose of each parameter. Provides context beyond 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?

Clearly states verb+resource: 'Fetch and cache a web component library's Custom Elements Manifest (CEM) from a CDN registry'. Differentiates from siblings by specifying CDN source (jsDelivr/UNPKG) and npm package name, which no other sibling tool does.

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?

Provides clear when-to-use context: 'Useful when the library is loaded via CDN without a local npm install'. Explains default behavior and when to set register:true. Does not explicitly mention alternatives or when not to use, but the context is sufficient.

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