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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description reinforces irreversibility with 'Permanently,' but adds nothing about side effects (e.g., whether the variable disappears from agent runtime config) or behavior on a missing ID.

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?

One front-loaded sentence with the destructive qualifier first and the identifying detail last; no filler.

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 simple single-parameter delete with annotations covering safety and no output schema, the definition is minimally sufficient. It is silent on not-found handling and on downstream effects of removing a variable, which an agent would want before invoking an irreversible operation.

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%, but with a single self-describing parameter the description's 'by variableId' matches the schema key and conveys that deletion targets one variable by identifier. No format, sourcing, or validation detail is added beyond that.

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 and resource ('Permanently delete a Convocore agent variable') plus the lookup key (variableId). It is clearly distinct from siblings like delete_agent, delete_agent_tool, and update_agent_variable, though it never explicitly contrasts itself with them.

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?

There is no guidance on when to use this versus update_agent_variable or get_agent_variable first to confirm the target. The word 'Permanently' hints at caution but no prerequisites, confirmations, or alternatives are named.

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