remove_sample_from_run

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

No annotations are provided, so the description must disclose behavioral traits. It only states what the tool does but fails to mention side effects, idempotency, permissions required, or error handling (e.g., what happens if sample is not associated). This is insufficient for safe use.

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 concise with no redundant text. However, it sacrifices informativeness for brevity; it could include key usage notes without becoming verbose. A score of 3 reflects acceptable but not optimal balance.

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?

The tool has an output schema (not shown) but the description does not explain return values. Given the simplicity of a removal operation, basic contextual details like confirmation or error responses are expected. Missing this makes it incomplete.

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 input schema defines two required string parameters (run_id, sample_id), but the description adds no extra meaning beyond 'identifier'. With 0% schema description coverage, the description should provide format, constraints, or examples, but it does not.

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 'Remove a single sample association from a run', specifying the verb 'remove', resource 'sample association', and context 'from a run'. It distinguishes from siblings like clear_samples_for_run (removes all) and associate_sample_with_run (adds), making the purpose unambiguous.

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 such as clear_samples_for_run (to remove all samples) or delete_sample_from_project (to delete from project). The description lacks context about prerequisites or when not to use it.

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