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

Annotations already declare readOnlyHint=true, so the safe-read behavior is covered. The description adds useful context by saying the response includes application types and permissions and by naming the underlying GET /applications endpoint, but it does not describe pagination behavior or any rate/auth constraints beyond the annotation.

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?

Two sentences with zero waste, front-loading the action and scope before the API endpoint detail. Every part earns its place by either describing the resource or grounding it in the underlying Basis Theory endpoint.

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 read-only list tool with no output schema and fully documented parameters, the description covers scope and returned fields well enough to call correctly. It could be slightly stronger by explicitly noting pagination behavior or routing the agent to get_application for single-item retrieval, but no critical information is missing.

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% and all three pagination/filter parameters (page, size, type) are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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?

States a specific verb (List), resource (applications/API-key holders), scope (in the tenant), and returned attributes (types and permissions). It does not explicitly name the sibling get_application as the single-resource alternative, but the list-vs-get distinction is clear enough for selection.

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 implies usage by stating it lists applications in the tenant, and the endpoint hint reinforces that this is a collection read. However, it gives no explicit when-to-use guidance, no exclusions, and does not name alternatives like get_application for retrieving a single application.

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