✓ SAFE: List SQLite DB files in a directory.

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

There are no structured annotations, so the description carries the burden. 'SAFE' and 'List' imply a read-only operation, which is useful but minimal. The description does not disclose whether it scans subdirectories, what file extensions are matched, or behavior with invalid directories.

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, front-loaded sentence that communicates the safety and purpose of the tool with no redundant or filler text. It earns its place.

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?

For a simple single-parameter listing tool, the description covers the essential operation. Given the low complexity and the existence of a 'directory' property, the missing details such as recursion or extension filtering are not critical for a competent agent, though the description could be slightly richer.

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 provides only a name and maxLength for the single 'directory' parameter with no description. The tool description mentions 'in a directory,' which clarifies that the parameter is the target path, but it offers no details on optional behavior, defaults, or accepted formats.

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?

Tautological: description restates name/title.

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 is provided about when to choose this tool over alternatives or when it is appropriate. The only implicit context is that it lists database files, but there is no explicit mention of when not to use it or what alternatives exist.

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