get_request

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

There are no annotations, so the description must convey behavior, and 'Get full details' does indicate a read operation that returns a comprehensive representation. However, it does not disclose authentication requirements, error handling, or what exactly constitutes 'full details'.

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?

A single, front-loaded sentence that immediately states the action and object. There is no filler or redundant explanation; every word contributes to the meaning.

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 straightforward get-by-ID tool, the description plus a fully documented schema are mostly sufficient. However, the lack of an output schema and annotations leaves the meaning of 'full details' unspecified, and the authentication parameters are only explained in the schema, not in the tool's usage context.

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?

All five parameters have descriptive schema entries, so the baseline is 3. The description adds only that requestId is the lookup key, which is already clear from the schema's 'Clockwork request ID' description.

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?

States a specific verb ('Get') and resource ('request'), and scopes it to a single request by ID, which distinguishes it from list_requests and get_latest_request. It could be stronger by naming those siblings, but the specificity is clear.

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 phrase 'by ID' implies the tool is for retrievals when a specific request identifier is already known. No explicit when-not-to-use guidance or alternative tools are mentioned, so the usage context is only implied.

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