delete_feature

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It explicitly warns 'Cannot be undone', 'permanently removes the feature table and all associated values', and 'All provenance information... will be lost', which goes beyond the minimal. It does not discuss permissions or error conditions, but the key destructive behavior is well covered.

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 well-structured with a clear warning, parameter list, and return value description. It is slightly repetitive ('Cannot be undone' and 'WARNING: This permanently removes...' convey similar information), but every section serves a purpose and the format is easy to parse.

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 tool's simplicity, the description is complete: it explains the destructive effect, parameters, and the return value. An output schema exists, so return details are further specified. No significant information gaps remain for a feature deletion tool.

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 no descriptions (0% coverage), so the description must compensate. It explains 'table_name: Table the feature is attached to' and 'feature_name: Name of the feature to delete', adding meaningful context beyond the parameter names.

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 'Delete a feature definition and all its values' with a specific verb and resource. It distinguishes itself from sibling tools like create_feature by focusing on deletion and explicitly mentioning the irreversible nature.

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 usage for deleting features and strongly warns about permanence, providing clear context. It does not explicitly name alternatives or exclusions, but the destructive nature and the warning make the appropriate use case evident.

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