Completion Entry Details

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

Annotations already mark it as read-only; description adds specifics about returned data (documentation, types, JSDoc, code actions) without contradicting annotations. Discloses additional behavioral traits beyond the read-only hint.

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 redundant information. Front-loaded with verb and resource, then details. Every sentence serves a purpose.

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?

No output schema, but description compensates by listing return values (documentation, type signature, etc.). For a 4-param tool with 100% schema coverage, the description provides sufficient context for an agent to invoke effectively.

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 covers all 4 parameters with descriptions; description adds minimal extra meaning (confirms multiple entries via entryNames). Baseline 3 is appropriate as schema does the heavy lifting.

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?

Description clearly states the tool retrieves full details for completion entries, explicitly lists included information (documentation, type signature, JSDoc, code actions), and distinguishes itself as a follow-up to completionInfo.

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?

Description positions it as a follow-up to completion_info, implying sequential usage. It does not explicitly mention when not to use or list alternatives, but the context is clear enough for an AI agent.

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