Update a USSD app

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds the behavioral trait 'Requires the `ussd` scope,' which is useful. However, it does not disclose implications of required parameters or mutability details beyond the schema.

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 two sentences, front-loading the core purpose with no wasted words. It efficiently conveys the action and a key requirement.

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 4 parameters, no output schema, and low schema coverage, the description lacks sufficient detail. It does not clarify required vs optional parameters, update semantics (e.g., partial vs full), or error scenarios, leaving the agent underinformed.

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 25% (only 'id' documented). The description lists the fields 'name, callback URL, or active state' but does not explain them meaningfully beyond the schema types. It omits the required 'id' parameter, and the 'or' phrasing is misleading given schema constraints.

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 'Updates an app's name, callback URL, or active state,' specifying the verb and resources. It distinguishes from sibling tools like `hellio_ussd_create_app`. However, the use of 'or' implies partial updates, but the schema requires both name and callback_url, creating slight ambiguity.

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 provides no guidance on when to use this tool over alternatives like `hellio_ussd_switch_app_mode` or `hellio_ussd_rotate_app_secret`. It only mentions the required scope, not usage context or exclusions.

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