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

With no annotations, the description carries the burden of explaining behavior. It does disclose what the returned record contains, such as price, turnaround, deliverables, pricing policy and limits. However, it does not state that the operation is read-only, how errors are handled, or whether any authorization or context is required.

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, focused sentence that front-loads the core purpose and then lists the record contents concisely. Every word adds value, with no filler or repetition of the tool name.

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 get-by-id tool with no output schema, the description provides enough information about the returned content to be useful. It could be more complete by noting how this differs from the catalog/list siblings, but the core invocation context is sufficiently covered.

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 schema already documents the single parameter 'id' with a clear example, so schema coverage is high. The description adds only slight context by referring to an 'engagement tier,' but it does not meaningfully expand on the parameter semantics beyond what the schema provides.

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 identifies the tool as returning a full record for one engagement tier, with a specific list of contained fields. It implies a single-record retrieval rather than a list operation, though it does not explicitly differentiate itself from sibling tools such as list_offers or search_catalog.

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 'for one engagement tier' implies this is for retrieving details of a single offer, which is useful context. However, there is no explicit guidance on when to use this tool instead of list_offers, search_catalog, or lookup_catalog, and no mention of exclusions or prerequisites.

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