kaiten_add_card_external_link

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds almost no behavioral context: it does not state that repeated calls create duplicate links (which the non-idempotent hint implies, but the description does not make explicit), what permissions are needed, or how the link is displayed on the card.

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 single short sentence contains no filler and specifies the action up front. Its terseness is a problem of under-specification, but relative to the conciseness dimension, the structure is efficient and easily scanned.

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 write operation with three parameters, 0% schema description coverage, and an output schema, the description is too thin. It leaves the meaning of the description parameter, duplicate handling, permission requirements, and link behavior unexplained, although the output schema does cover the return shape.

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 description does not explain any of the three parameters, and the schema description coverage is 0%. 'Link to a card' implies card_id and url, but there is no information about the URL format/length or about the optional description field, and the description does not compensate for that gap.

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 verb 'add' and the resource 'external link' and identifies the target ('to a card'), so an agent can distinguish this tool from its siblings kaiten_update_card_external_link and kaiten_remove_card_external_link. The word 'native' is the only vague part and is not explained.

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?

The description gives no guidance on when to use this tool instead of alternatives. It does not say whether to link via the description text, does not mention prerequisites such as card existence or permissions, and does not explain what happens when the same URL is added twice.

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