update-database

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

No annotations exist, and the description only indicates mutation (update). It fails to disclose whether the operation is idempotent, what happens on conflict, required permissions, or if it replaces or merges the database.

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 is very concise, but the brevity sacrifices clarity for an operation like JSON Patch, which might need more explanation.

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?

Given no output schema and no annotations, the description is too sparse. It does not explain the format of operations, expected return value, or how errors are handled, leaving the agent with insufficient 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?

Input schema covers both parameters with descriptions ('Database UUID' and 'JSON Patch operations'). Description repeats 'JSON Patch operations' but adds no new semantics beyond schema, which has 100% coverage.

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 the tool updates a database using JSON Patch operations, distinguishing it from create/delete/get database tools. However, it does not specify the scope of updates or how JSON Patch is applied.

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 on when to use this tool versus alternatives like create-database or delete-database. Among many update tools, no differentiation is provided.

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