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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds the useful concrete detail that it calls only that one endpoint and returns the raw response, but says nothing about result size limits despite advertising 10000+ entities.

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?

Three short sentences, front-loaded with the endpoint contract. The leading 'Labeled Accounts.' merely restates the title and earns little, but overall there is minimal waste.

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?

An output schema exists, so return values need not be explained, and the schema fully documents parameters. Only the pagination/result-volume behavior for a 10000+ entity dataset is left unaddressed.

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%, so all seven parameters are self-documenting; baseline is 3. The description's mention of CEX/KOL/VC/entity name/address loosely maps to labels, entityName, and accountAddress but adds no syntax or semantics beyond the schema.

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 gives a specific verb+resource (fetching labeled wallets, programs and accounts) and names the exact endpoint GET /v4/wallets/labeled-accounts. It doesn't distinguish itself from the sibling list-labeled-programs, which is a notable overlap given both surface labeled entities.

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?

It says what can be filtered (CEX, KOL, VC, entity name, address) but never states when to choose this tool over list-labeled-programs or other list-* siblings. Usage is implied by the filter categories rather than explicitly framed.

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