Spl-token Freeze Account

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

The description adds key behavioral context beyond annotations: it explains the effect ('prevents all transfers') and the authority requirement. Annotations already indicate a write operation (readOnlyHint=false), and the description aligns. However, it does not mention reversibility or state transitions, which would enhance transparency.

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 first sentence is concise and front-loaded. However, the description includes redundant boilerplate about 'SAP MCP context' and generic warnings about confirming values, which add length without specific value. It could be more focused.

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?

Given the low complexity (3 required parameters, no enums) and presence of an output schema, the description is adequate but lacks details on edge cases (e.g., already frozen accounts) or side effects. It does not reference related tools like thawAccount, which would improve 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 100% coverage with clear descriptions for each parameter (mint, account, freezeAuthority). The description does not add additional parameter-level detail beyond what the schema provides, so a baseline score of 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?

The description clearly states 'Freeze a token account (prevents all transfers).' This is a specific verb and resource, and it distinguishes the tool from siblings like thawAccount and transfer, which have opposite or different behaviors.

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 mentions 'Requires freeze authority' as a prerequisite but does not explicitly guide when to use this tool over alternatives like thawAccount or when freezing is appropriate. The generic advice about token operations and SAP context does not provide specific selection criteria.

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