delete_sample_from_project

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

No annotations provided, so description carries full burden. It discloses irreversibility and superuser restriction, which are key behavioral traits. Could add details on cascading effects or what happens to underlying data.

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: two lines with key info (purpose, access, irreversibility) plus a docstring-style parameter list. No wasted words.

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?

Adequately complete for a delete operation: purpose, required permissions, parameters, and irreversibility. Output schema exists, so return value explanation not needed. Minor gap: no clarification on whether deletion is permanent or if sample can be recovered.

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%, and description adds meaningful parameter descriptions: 'The project identifier' and 'The sample identifier to delete'. This goes beyond the schema's minimal type and title.

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 verb 'Delete', resource 'sample from a project', and critical scope 'superuser only, irreversible'. This distinguishes from siblings like add_sample_to_project or remove_sample_from_run.

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?

Mentions 'superuser only' as a prerequisite but does not explicitly provide when-to-use or when-not-to-use guidance relative to sibling tools. Usage is implied for deletion but no alternatives mentioned.

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