Metis — List Basket

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

Discloses that private/ subfolder is never listed, adding behavioral context beyond a basic read operation. No annotations exist, so description carries full burden; it could mention read-only nature explicitly but does not mislead.

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?

Two concise sentences, each purposeful: first states core function, second adds critical exclusion. No fluff or redundancy.

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?

Completely describes a simple list tool with no params and an output schema; explains the basket concept and privacy constraint, sufficient for agent invocation.

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?

No parameters exist in the schema, and schema coverage is 100%. Baseline of 4 applies; description adds no param info as none required.

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?

Description states specific verb+resource ('List files in the Metis basket') and distinguishes from sibling tools like 'list_folder' by defining the basket's role (legacy & inspiration documents) and explicitly excluding the private/ subfolder.

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?

Implies usage for listing basket files and notes the exclusion of private data, but does not explicitly compare to other list tools or provide when-not scenarios.

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