update_database

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

With no annotations, the description lacks details on side effects, permissions, or reversibility. It only says 'update' without clarifying what happens to existing data, error conditions, or whether the operation is idempotent.

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 concise sentence, which is efficient but lacks necessary details. It earns a middle score because it is not verbose but missing critical 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?

Given the complexity of updating a database in OpenMetadata and the absence of an output schema, the description is incomplete. An agent needs to know what fields are updatable and the structure of database_data, which is not provided.

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 has 0% description coverage for parameters. The description does not explain what 'database_data' object should contain or the format expected. The parameter names are self-explanatory but insufficient for correct usage.

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 clearly states the verb 'update' and the resource 'database' in OpenMetadata, distinguishing it from other tools like create_database or delete_database. However, it is generic and does not specify which fields can be updated.

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 on when to use this tool versus alternatives like create_database or get_database. There is no mention of prerequisites, such as the database needing to exist, or when a partial update is applicable.

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