Create a USSD app

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

Annotations indicate a write operation without destructiveness. The description adds context: starts in test mode, returns secrets shown once, requires ussd scope. No contradiction with 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 three sentences, concise, and front-loaded with the core action. Every sentence adds value without 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?

Given 3 parameters, no output schema, and many siblings, the description covers creation mode, secrets, and prerequisites. It lacks explicit return value format but mentions key outputs (test_secret, live_secret).

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% (callback_url has a description). The tool description reinforces callback_url must be public but provides no additional details for name or active parameters, leaving room for ambiguity.

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 it creates a USSD app that points a short code to a callback URL. It distinguishes itself from sibling tools like hellio_ussd_delete_app and hellio_ussd_update_app by specifying creation with test mode and secret return.

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 implies usage for creating a USSD app and mentions prerequisites (public callback URL, ussd scope), but does not explicitly state when to use this tool over alternatives or when not to use it.

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