stat

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

Echoes annotation readOnlyHint with 'Read-only, no side effects'. Adds value by detailing return format (structured JSON) and specific metadata fields.

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 sentence serves a purpose. Front-loaded with main verb and details.

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?

Adequate for a simple tool with 1 required parameter and existing annotations. References sibling tools.

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%, so description adds minimal extra meaning. 'Paths to inspect' is clear but not beyond 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?

Description clearly states 'Return detailed file metadata' and lists specific fields (size, permissions, etc.). Distinguishes from sibling 'ls' and 'du'.

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?

Explicitly says when to use (inspect attributes without reading contents) and when not (not for directory listing, use 'ls'). Provides alternatives 'ls' and 'du'.

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