✓ SAFE: Open an existing database file. Sets as current context. Returns database info. Errors if file does not exist — use create_database to make a new one.

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

Discloses key behaviors: sets current context, returns database info, errors on missing file. However, lacks details on side effects like file locking or memory loading. With no annotations, this is still good coverage.

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?

Single sentence with a dash for contrast, no wasted words. All critical info is front-loaded and efficient.

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?

Covers purpose, usage, and basic behavior well. Missing parameter documentation and return format details, but for a simple tool with no output schema, it is largely sufficient given sibling context.

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% and the description does not explicitly explain the 'path' parameter beyond implying it's a database file. No format, constraints, or usage hints provided, leaving a gap for the agent.

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?

Explicitly advises to use this tool only if the file exists, otherwise use create_database. This provides clear when-to-use and when-not-to-use guidance.

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