kaiten_list_external_links

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

No annotations are provided, so the description carries the behavioral burden. 'List all external links on a Kaiten card' clearly communicates a read-only operation with a defined scope. It does not mention pagination or return shape, but for a simple list operation the behavioral contract is sufficiently clear.

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 sentence, front-loads the action and object, and contains no filler or redundancy. Every word earns its place.

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?

With one parameter, full schema coverage, and no output schema, the description gives enough context to select and invoke the tool correctly. A note about the returned link fields would be helpful but is not essential for a straightforward list call.

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 description coverage is 100%: the single required card_id parameter is already documented as an integer 'Card ID'. The description adds no additional parameter meaning, but none is needed since the schema fully covers the only argument.

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 names a specific verb ('List'), a precise resource ('external links on a Kaiten card'), and scopes the result set with 'all'. This clearly distinguishes it from sibling tools like kaiten_create_external_link, kaiten_delete_external_link, and kaiten_list_documents.

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 intended use is implied: select this tool when you need the external links attached to a Kaiten card. However, there is no explicit when-not-to-use guidance or reference to alternative tools, so the routing decision relies mostly on inference.

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