Api task nodes remove evidence create

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the agent knows this is a destructive mutation, but the description adds nothing beyond that. It does not say what is destroyed, whether it can be undone, whether permissions are needed, or what happens to the underlying evidence asset versus the task node link.

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?

There is nothing wasteful because there is essentially nothing there: one identifier string. This is under-specification rather than conciseness, and there is no front-loaded statement of intent.

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?

A destructive, non-idempotent mutation with an undocumented required identifier, no output schema, and no annotations explaining scope. The description would need to carry essentially the whole burden here and it carries none of it.

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 single parameter 'id' has 0% schema description coverage and the description supplies no meaning at all. The critical ambiguity — whether 'id' identifies the task node, the evidence, or the task-node-to-evidence link — is left entirely unresolved, which makes a destructive call especially risky.

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 is a verbatim echo of the tool name, 'api_task_nodes_remove_evidence_create', giving the agent no human-readable statement of what it does. It is impossible to tell whether this deletes an evidence record, unlinks an evidence attachment from a task node, or creates a removal request — a distinction that matters against siblings like ciso_assistant_api_task_nodes_evidences_list and ciso_assistant_api_evidences_destroy.

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 when-to-use guidance, no prerequisites, no alternatives, and no exclusions of any kind. The agent has no basis for choosing this over ciso_assistant_api_task_nodes_destroy or ciso_assistant_api_task_nodes_partial_update.

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