list_external_links

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

The annotations already establish that this is read-only, idempotent, and non-destructive. The description adds only 'given entity' and 'optionally filtered by provider', which are also visible in the schema. It does not mention result shape, pagination, or other runtime behavior beyond what the call itself implies.

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 that front-loads the verb, object, scope, and optional filter. There is no filler and no repetition of obvious schema details.

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?

It is largely sufficient for a simple read-only listing tool, especially with strong annotations and a small well-understood parameter set. However, there is no output schema and the description doesn't describe the shape of the links returned or any pagination/filtering behavior, so it leaves a small gap.

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 67%, with entityId and provider already described and entityType constrained by enum. The description loosely mirrors these with 'given entity' and 'filtered by provider', but it adds no substantive semantic detail beyond the schema's existing documentation.

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 uses a specific verb 'List' and names a specific resource: 'external ticket links for a given entity'. It also notes the optional provider filter, making the tool's scope immediately clear and distinguishing it from add_external_link and remove_external_link.

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 clear context: to use this tool when they want to display external ticket links for an entity, optionally narrowed by provider. It doesn't explicitly name alternatives or state when this tool should be avoided, so it falls just short of full guidance.

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