get_whitelist

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

No annotations are provided. The description uses 'View' which suggests a read-only operation, but it does not confirm non-modification or disclose any behavioral traits like required permissions or actions upon missing parameters.

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 extremely concise with a single sentence, but it lacks necessary detail for a complete understanding. Conciseness is good but does not compensate for missing information.

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 view tool with no output schema, the description should explain what is returned (e.g., list of wallets). It is too minimal given the complexity of the parameter set and the absence of annotations.

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 coverage is low (33%) as only 'wallet' has a description. The tool description does not explain the meaning of 'token' (e.g., address vs. symbol) or 'limit', leaving ambiguity 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 clearly states 'View whitelist for a frozen token,' specifying the verb (view), resource (whitelist), and context (frozen token). It distinguishes from sibling tools like whitelist_wallets which manage the whitelist.

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 tool versus alternatives such as pm_manage_whitelist or whitelist_wallets. The description implies it's for viewing only but does not clarify scenarios or prerequisites.

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