get_token_list

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

No annotations are provided, so the description carries full burden. It fails to mention important behaviors like pagination, ordering, empty results, or whether it only returns tokens owned by the user. The one-sentence description is insufficient.

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?

Very concise and front-loaded with the verb 'List/search'. However, brevity comes at the cost of completeness; a bit more detail would improve without damaging conciseness.

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 3 parameters with low schema coverage, no output schema, and no annotations, the description is too minimal. It does not explain return format, pagination, or scope of the listing. Sibling tools add confusion without differentiation.

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 only 33% (dev param described). The description adds nothing beyond repeating the dev filter. Parameters 'search' and 'limit' are not explained. Much meaning is missing.

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 the tool lists/searches tokens and specifies a filter by creator, which gives a clear verb+resource. However, it does not distinguish from siblings like get_token_detail or get_token_state, which are also about tokens.

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 guidance on when to use this tool versus alternatives like get_token_detail or get_my_tokens. The description implies a general listing but context about scope or comparison to other list tools is absent.

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