planka_delete_custom_field_value

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

No annotations exist. The description only states the basic action without disclosing behavioral traits such as idempotency, side effects, permissions required, or error handling. For a destructive operation, more detail is needed.

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 a single, focused sentence that is efficient and front-loaded. However, it could incorporate a bit more context without losing conciseness.

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 deletion tool, the description adequately states the core function. However, lacking output schema and behavioral details, it feels incomplete, especially given the complexity of the parameter structure and sibling operations.

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 tool description does not add any meaning beyond what the input schema already provides. Although the schema includes parameter descriptions, the description misses the opportunity to clarify relationships or constraints.

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 the action ('Delete'), the resource ('custom field value'), and the context ('from a card'). It effectively distinguishes from sibling tools like 'set_custom_field_value' (modify) and 'delete_custom_field' (delete entire field).

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. There is no mention of prerequisites, when deletion is appropriate, or how it differs from modifying or clearing the value.

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