drop_table

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

With no annotations, the description carries full behavioral disclosure. It reveals that the operation permanently removes stored rows and clarifies that scraped pages are unaffected, which are key side effects. It does not mention return behavior or potential errors, but for a delete operation this level of transparency is solid.

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 two concise sentences, front-loaded with the primary action and followed by a clarifying side-effect statement. Every word earns its place, no fluff or redundancy.

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?

This is a simple tool with one parameter and an output schema, so the description need not explain return values. It covers the core action, permanence, and non-effect on scraped pages, which is sufficient for an agent to use it correctly. The only gap is parameter description, but that is accounted for in parameter semantics.

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%, meaning the parameter 'name' has no description in the schema. The description does not explicitly describe the parameter; it only implies via 'Delete a saved result table' that 'name' identifies the table. This is minimal compensation for a low-coverage schema. A more explicit statement like 'name: the name of the table to delete' would be expected.

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 tool's action: 'Delete a saved result table' with a specific verb (delete) and resource (result table). It also clarifies that it permanently removes rows but leaves scraped pages unaffected, which distinguishes it from other table-related tools like get_table, export_table, and query_table. This is a precise and unambiguous purpose statement.

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 provides clear context: it deletes a saved table and is permanent, implying use when a table is no longer needed. It does not explicitly mention alternatives or when not to use it, but the action is self-evident and the permanence note adds caution. Lacks explicit sibling differentiation but is adequate for an agent to decide.

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