get_capture

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

With no annotations, the description carries full burden. It discloses the return envelope format on success and structured error dict on failure. It also lists all format options and their effects. However, it does not mention rate limits, authentication needs, or potential side effects, which are minor for a read operation.

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 well-structured with a summary line followed by Args and Returns sections. It is concise yet complete, with no unnecessary words. Every sentence provides essential information, and the most important information (fetching a single capture) is front-loaded.

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 complexity (multiple format options) and the presence of an output schema, the description covers all necessary aspects: purpose, parameters, return format, and error behavior. It is sufficient for an agent to understand and use the tool 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 description coverage is 0%, so the description must compensate. It fully describes both parameters: capture_id as 'the capture ULID' and format with explicit enumeration of options (json, markdown, vault-frontmatter, legacy-markdown) and default. This adds significant value beyond the schema.

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 explicitly states 'Fetch a single capture by id, in the requested format.' It clearly identifies the verb, resource, and scope, distinguishing it from sibling tools like list_captures (multiple captures) and refetch_capture (re-fetching).

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 does not explicitly state when to use this tool versus alternatives or provide exclusions. It implies usage for retrieving a single capture but lacks explicit guidance on when not to use it or comparisons with siblings.

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