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

With no annotations, the description carries the full burden. It states what is included in the return (trust breakdown, callable endpoint), implying a read operation, but does not explicitly confirm it is read-only, mention permissions, or describe side effects. Adequate but could be more explicit about safety.

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?

Single sentence, front-loaded with the core purpose. No wasted words; every part adds value. The description is concise and well-structured.

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?

Given the simple input (one string ID) and no output schema, the description covers the key output aspects (trust breakdown, callable endpoint). It does not mention error handling or behavior for invalid IDs, but for a straightforward get-by-id tool this is nearly complete.

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% with a clear example for offering_id. The description adds no additional meaning for the parameter itself beyond what the schema provides. Baseline 3 is appropriate since the schema sufficiently documents the single required parameter.

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 explicitly states 'Fetch the full detail of a single offering by id', clearly identifying the action (fetch) and resource (offering). It also mentions included content (trust breakdown, callable endpoint), distinguishing it from sibling tools like aicom_search_offerings which handle lists.

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?

Usage is implied: to get details of a specific offering by its id. However, no explicit guidance is given on when to use this vs alternatives (e.g., aicom_search_offerings for listing) or when not to use it. Missing contextual cues like prerequisites or exclusion criteria.

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