List USSD apps

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

The description adds pagination type (cursor), ordering (newest first), and auth requirement beyond the annotations (readOnlyHint, openWorldHint). It does not detail potential side effects or rate limits, but for a read-only list, these are less critical.

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?

One sentence, front-loaded with the most important information (list, pagination, ordering, scope). Every part is essential and there is no redundancy.

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 simple list tool with readOnlyHint and openWorldHint, the description covers the main behavioral aspects. No output schema is provided, which could be a small gap, but the description is otherwise sufficient for an agent to understand usage.

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 50%; only cursor has a description in schema. The tool description mentions 'cursor-paginated' which adds context for cursor param but does not explain per_page further. It partially compensates for the schema gap but still leaves per_page under-described.

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 'Cursor-paginated list of your USSD apps, newest first.' This specifies the verb (list), resource (USSD apps), and key traits (paginated, ordering). It distinguishes itself from sibling tools like create, delete, or update.

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 the required 'ussd' scope, giving a prerequisite. It does not explicitly compare to alternatives, but the purpose is clear enough for a simple read operation. Lacks explicit when-not-to-use guidance.

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