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

With no annotations, the description carries the full burden. It discloses the paid nature ($0.002/req or pass) and the output scope (all wire items), but does not mention error behavior, authorization requirements, or rate limits. The 'or pass' wording is vague, adding some uncertainty rather than full transparency.

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 extremely concise, with the core action in the first sentence and a clear Args section for the parameter. No fluff or redundancy; every word 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 get tool, the description covers the essential purpose, parameter source, and return content (all wire items). It does not describe a response schema, but given the tool's simplicity, the description is reasonably complete. Minor gaps remain around error cases and output structure details.

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 only names the parameter with minimal title, but the description fully compensates by explaining thread_id is the id returned by list_threads or search_wire. This gives the agent actionable guidance on how to obtain a valid value, adding significant meaning 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 clearly states the tool retrieves a single event thread with all its wire items, using a specific verb (get) and resource (thread). It distinguishes itself from sibling tools like get_article, get_context, and list_threads by focusing on thread-specific wire items.

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 provides usage context by stating the thread_id should come from list_threads or search_wire, indicating this tool is intended for fetching a specific thread after listing/searching. It does not explicitly name alternatives to avoid, but the guidance on where to obtain the ID implies the correct workflow.

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