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

readOnlyHint=true already tells the agent this is a safe read. Beyond that the description adds only that results carry 'types and permissions'; it says nothing about pagination behavior, result volume, or any auth/rate-limit constraints, which for a paginated list tool is a real gap.

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 short sentences, zero filler. The scope statement leads and the endpoint reference trails, so the most important information is front-loaded.

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 no output schema, the description usefully hints at returned content ('types and permissions'), and pagination inputs are fully documented in the schema. Complete enough to call correctly, though it omits any note about how paging results are shaped or how many records to expect.

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%: page, size, and type are all documented in the schema with examples for type and bounds for page/size. The description adds no parameter detail, so the baseline 3 applies.

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) and resource (applications), and clarifies the domain term by noting these are API-key holders in the tenant. The 'GET /applications' reference pins the operation precisely, distinguishing it from the singular basis_theory_get_application sibling, though it never names that alternative.

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 explicit guidance on when to use this versus basis_theory_get_application, basis_theory_list_tenant_members, or the other list tools. Usage is only implied by 'List ... in the tenant' and the endpoint reference; no prerequisites or exclusions are given.

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