show

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

States '[read-only]' upfront, indicating no mutation. No annotations are provided, so the description carries the burden. However, it lacks details on authentication, rate limits, or side effects beyond the read-only hint.

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?

Extremely concise, single line, well-structured with delimiters. Every element provides value without repetition.

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 15 optional parameters and no schema descriptions, the description offers a high-level overview but lacks completeness. An output schema exists, reducing the need to explain return values, but missing parameter details and usage context hurt completeness.

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 0%; the description groups parameters (target/scope, filters, result shape, mode, plumbing) and adds format hints for 'period'. This compensates partially, but individual parameter meanings (e.g., 'query', 'openbox') remain unclear.

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 indicates a read-only operation for displaying items with filters and options. It specifies targets, filters, and result shape, distinguishing it from sibling tools by its generic listing role.

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?

No guidance on when to use this tool versus alternatives like 'brief' or 'report'. The description only lists parameters without context for selection.

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