yaaif_file_artifact_delete

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

No annotations provided, so description must carry behavioral info. It discloses the HTTP method (DELETE) and the requirement of confirm=true. However, it does not mention that the operation is irreversible, whether it affects other resources, or any error conditions. Adds some value but not comprehensive.

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?

Single sentence with no filler, front-loaded with action and scoping. Efficient and to the point.

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 4-parameter tool with no annotations and no output schema, the description covers the main delete behavior and confirm requirement but omits the required artifact_name parameter and session_id semantics. It is adequate but not fully complete.

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?

Description explains the meaning of 'version' (optional) and 'confirm' (must be true), but does not explain 'artifact_name' or 'session_id'. With 0% schema coverage, it partially compensates but misses two params. It does clarify the core behavior of version scoping.

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?

States a specific verb 'Delete' with resource 'artifact version' and clarifies scope: one version (?version=N) or all when omitted. Distinguishes from sibling tools like yaaif_file_artifact_versions (list) by the delete action.

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 explicit comparison to alternative tools or conditions for when to use instead of other file operations. The context is implied (deletion), but no mention of when to use vs list/load tools or exclusions.

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