get_capsule

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves metadata, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what metadata fields are returned. The description is minimal but doesn't contradict any annotations.

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 two sentences with zero waste: the first states the purpose, and the second provides usage guidelines. It's front-loaded and appropriately sized for a simple retrieval tool.

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?

Given the tool's low complexity (1 parameter, no annotations, but has an output schema), the description is reasonably complete. It covers purpose and usage well, but lacks details on behavioral aspects like permissions or error handling. The output schema likely handles return values, so this isn't a major gap.

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 meaning beyond the input schema by clarifying that 'capsule_id' must be a 'known capsule ID', implying it should be an existing identifier. With 0% schema description coverage and only 1 parameter, this compensates adequately, though it doesn't specify format or constraints.

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 verb 'Retrieve' and the resource 'metadata for a specific capsule by its ID', making the purpose specific and unambiguous. It distinguishes from sibling tools like 'search_capsules' by explicitly stating it's for fetching metadata for a known ID, not for searching.

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 provides explicit guidance on when to use ('Use only to fetch metadata for a known capsule ID') and when not to use ('Do not use for searching'), with a clear alternative implied by the sibling tool 'search_capsules'. This gives the agent precise context for tool selection.

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