get_item

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 return content but does not explicitly state that the operation is read-only, how errors are handled, or any auth/rate-limit constraints. For a simple retrieval tool, it is adequate but not comprehensive.

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 sentence that front-loads the core purpose ('Full detail for one saved item') and efficiently lists the output fields with no redundant words.

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 tool's simplicity (1 parameter, no output schema), the description adequately covers what the tool does and what it returns. It could be improved by explicitly guiding when to use it, but it is mostly complete for an agent to recognize its purpose.

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% for the only parameter (message_id) with a clear description. The tool description adds context about why the id is used (to get full detail) but does not add new semantic details 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 full detail for one saved item, listing specific fields (transcript, summary, OCR text, visual description, locations, URL). This distinguishes it from siblings like search_bucket and list_recent which are for finding items, and download_video/save_to_bucket for other operations.

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 use when you need complete details for a single item, but it does not explicitly state when to use versus alternatives. The schema parameter description mentions 'from search_bucket or list_recent' but that is outside the tool description itself.

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