get_request

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

With no annotations provided, the description carries the full burden. It explicitly states what the tool returns (method, path, query, headers, body) and that it targets a single captured request. The 'Get' verb implies a read-only operation, and the description adds detail about the response content beyond what the name alone suggests.

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 a single sentence that is front-loaded with the action and object, providing all essential information with zero redundancy. It effectively lists the returned fields without extra fluff.

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 simple tool with one parameter, no output schema, and no annotations, the description is entirely sufficient. It clearly defines what the tool does, what data it returns, and the input required. There are no significant gaps given the tool's simplicity.

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 input schema fully describes the 'id' parameter, including format and example ('The request id from list_requests, e.g. "3"'). The description itself does not add additional meaning beyond mentioning 'by id,' but since schema coverage is 100%, the needed semantics are already present.

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 uses a specific verb 'Get' with a precise resource: 'full detail (method, path, query, headers, body) of one captured request by id.' This clearly differentiates from siblings like list_requests (which lists requests) and replay_request (which likely alters state).

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 implies usage after obtaining an id from list_requests, as the parameter description states 'The request id from list_requests.' It clearly identifies the tool for retrieving full details of a single request, though it does not explicitly mention when not to use it. The context of sibling tool names reinforces the appropriate use case.

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