show-item

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

With no annotations provided, the description must fully disclose behavioral traits, but it only states the action without revealing whether the operation is read-only, what the return format is, or any prerequisites. The agent cannot tell if showing an item changes state or requires specific permissions.

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 very concise (one sentence), but it is slightly under-informative. It efficiently states the core function but omits details that would improve usability, such as how 'show' behaves. It is not overly verbose, but could be expanded to better guide the agent.

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 low parameter count and lack of output schema, the description partially covers the tool's purpose. However, it does not explain what the agent should expect as a result (e.g., a visual display or data return) and does not differentiate from the many sibling tools that also retrieve lists or items.

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 covers 100% of parameters with descriptions, but the tool description adds value by clarifying that the 'id' parameter can be either an item ID or a special list name (e.g., inbox, today). This goes beyond the schema's generic description and helps the agent understand the parameter's dual role.

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 'Show a specific item or list in Things' clearly states the action (show) and the resource (item or list in Things). It distinguishes itself from sibling tools like get-inbox or search-todos by covering both specific items and predefined lists in one tool.

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 does not provide any guidance on when to use this tool versus alternatives like get-inbox, get-today, etc. There is no explicit context for when the tool is appropriate or when it is not, leaving the agent to infer usage from the tool name alone.

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