planka_create_task_list

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

The description implies a write operation ('Create') but provides no additional behavioral context such as authorization requirements, side effects, or limitations. With no annotations present, the burden is on the description, which falls short.

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 efficient sentence that is front-loaded with the action and object. There is no fluff or redundancy.

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?

Given the simple tool (two required string params, no output schema), the description lacks context about what a task list is, how it relates to cards, or any behavior beyond creation. The parameter descriptions in the schema help, but the tool description itself is 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 tool description adds no meaning beyond the input schema. Although the schema itself includes descriptions for 'name' and 'card_id', the coverage metric shows 0% because the description does not reference or elaborate on parameters. The description fails to compensate for low schema_description_coverage.

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 'Create a named task list on a card' clearly states the action and resource. It is specific enough to distinguish from siblings like 'planka_add_task' (adds a task to a list) or 'planka_create_list' (creates a list on a board), though it does not explicitly compare 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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives, nor does it mention prerequisites like the need for an existing card.

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