uc_schema_delete

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

Annotations already mark destructiveHint=true, but description adds no further behavioral context. Does not state that deletion is irreversible, that it deletes all contained objects, or any rate limits or authorization needs. With annotations present, the description should add value beyond them, but it does not.

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?

Extremely concise: one sentence with the endpoint. No fluff, front-loaded with the essential action. Every word 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 delete tool with a single parameter and output schema present, the description is minimally adequate. However, it could mention that the action is permanent and affects child objects. The output schema is not shown, but description needn't explain return values. Context signals indicate complexity is low, so a 3 is reasonable.

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% (full_name parameter well-described as 'Schema full name (catalog.schema)'). The description does not add any extra meaning about the parameter beyond the schema, so baseline score of 3 is appropriate.

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 action 'Delete a schema' and provides the API endpoint. The verb 'delete' and resource 'schema' are unambiguous. Among sibling tools (create, get, list, update), this tool's purpose is distinct.

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 vs alternatives. For example, does not indicate that schema must be empty or that tables will be cascaded. No mention of prerequisites or situations where update or get would be more appropriate.

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