update-database

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool uses JSON Patch operations, which indicates it supports partial updates. However, it omits details such as whether the database must exist, what happens on failure, or any authorization requirements.

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 sentence of 7 words, front-loading the key action and method. Every word adds value, and there is no redundancy or unnecessary information.

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 tool with no output schema and moderate complexity (JSON Patch), the description is minimal. It doesn't explain that the database must exist beforehand, nor does it mention return behavior or error handling. However, it covers the essential purpose and method, making it adequate but not rich.

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% with both parameters described. The description adds the context of 'JSON Patch operations', which clarifies the expected format for the operations parameter beyond the schema's generic 'JSON Patch operations' description. This adds modest value, meeting the baseline of 3.

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 uses a specific verb-resource-method combination: 'Update a database using JSON Patch operations'. It clearly distinguishes from sibling tools like create-database, delete-database, and get-database by specifying the update action and the method (JSON Patch).

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?

The description implies the tool is used to update an existing database but provides no explicit guidance on when to use it versus alternatives (e.g., create-database for new databases). It lacks when-not-to-use instructions or context about prerequisites.

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