get_inquiry_conversation

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

The readOnlyHint annotation already communicates that this is a read operation, so the description does not need to restate that. The description adds useful context about what the response contains (messages and inquiry details), but it does not disclose anything about errors, authorization, or size/pagination behaviors.

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 communicates the action, target, and included content with no redundant words. Every element earns its place.

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 single-parameter read tool with a readOnlyHint annotation, the description is sufficient: it tells the agent what the tool returns and where the UUID comes from. There is no output schema, but the description covers the return content well enough; only minor details such as ordering or response shape remain unspecified.

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 coverage is 100% and the only parameter, uuid, is described as 'Inquiry UUID from list_inquiries,' so the schema does the heavy lifting. The description adds the 'vendor inquiry' framing but not additional parameter-level detail 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 states a clear verb and resource: 'Get full conversation for a vendor inquiry,' and specifies the contents via 'including messages and inquiry details.' It is clear enough to distinguish from sibling read tools like list_inquiries, though it does not explicitly name a sibling it is not.

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 conveys the use case: fetching a full conversation for a vendor inquiry with messages and details)Skip – this implies it is the deeper dive compared to list-only tools. The parameter description adds guidance that the UUID comes from list_inquiries, but there is no explicit when-not-to-use or alternative routing.

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