Get Inquiry

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description need not repeat safety. The description adds value by mentioning that the result includes 'full detail' and specifically 'thread_ids for messaging,' giving behavioral context beyond structured fields. No contradictions.

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 one concise sentence, front-loaded with the action verb, and includes only necessary detail about output content. Every word earns its place; no fluff or redundancy.

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 get-by-id tool with rich annotations and one parameter, the description is adequate. It states the resource, the scope (full detail), and an output element (thread_ids). It does not describe return format or error conditions, but those are not critical given the simplicity and existing annotations.

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 has no descriptions (0% coverage), so the description must compensate. The description says 'by id,' clarifying that the required integer parameter is the inquiry identifier. While minimal, it directly addresses the single parameter's purpose.

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 action: 'Fetch a single inquiry by id' with a specific verb and resource. It also notes 'full detail, including thread_ids for messaging,' which distinguishes it from list_inquiries and other siblings that may return summaries.

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 when to use this tool: when you need a single inquiry's full detail, including thread_ids. It does not explicitly exclude alternatives or name a sibling, but the context of siblings like list_inquiries and get_message makes the use case clear. No explicit when-not-to-use guidance, but sufficient for a simple fetch.

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