androidapi_send_ussd

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

Description implies a write operation (sending USSD), which matches 'readOnlyHint: false'. Does not detail potential side effects like carrier costs, response handling, or whether the request is blocking. Annotations already indicate not read-only and not destructive, but additional context would help.

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?

Two sentences, both essential. First states purpose with example, second provides prerequisite. No fluff, well front-loaded.

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 'send' tool with no output schema, the description is adequate but lacks mention of return value (likely USSD response string) and potential costs. Could be more complete given the tool's interactive nature.

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 covers all 3 parameters (100% coverage). Description adds a code example and hints at using get_devices for device ID. This adds marginal value, so baseline 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?

Clearly states the verb 'Send' and the resource 'USSD / MMI request' with an example ('check balance with *123#'). Differentiates from sibling tools that deal with contacts, SMS, WhatsApp, etc.

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?

Provides one usage hint: 'Use androidapi_get_devices to get valid device IDs.' But does not specify when to use this tool over alternatives like androidapi_get_ussd or androidapi_delete_ussd.

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