Spl-token Get Token Accounts

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

The description contradicts annotations: it says 'operation class write' but annotations set readOnlyHint=true. This is a serious inconsistency. No additional behavioral context is provided beyond the annotations.

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 not concise; it includes extraneous information about SAP MCP context, operation class, and parameter aliases that are irrelevant or contradictory. The important core statement is front-loaded but diluted by unnecessary 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?

For a read-only tool with no parameters and an output schema, the description briefly mentions output (balances and metadata) but lacks details on pagination, rate limits, or data format. The contradictory claims undermine completeness.

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?

The input schema has no parameters, but the description mentions parameter aliases (owner, address, pubkey) without explaining how they are used. This creates confusion as there are no parameters to alias. The description does not add meaningful semantics.

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 main sentence clearly states the tool lists SPL token accounts with balances and metadata. However, the description also includes misleading statements like 'operation class write' and suggests it should be used for deploy, mint, transfer, etc., which are not this tool's function.

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 includes vague usage guidance like 'Use token tools alongside SAP payments...' but does not specify when to use this tool versus alternatives or provide explicit when-not conditions. It misleadingly suggests using it for write operations.

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