Phone Buttons

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

With no annotations, the description carries the full burden; it does disclose that passing []/none clears buttons and that a tap is delivered as kind 'button' {id, label, heard}, which is genuinely useful. It does not clarify whether a new list replaces the entire existing set or appends, nor any scope/permission behavior for the 'sender' target.

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 tight sentences with zero filler, and the payload/clearing rule is front-loaded. The semicolon-separated 'or plain labels; [] or none' is slightly dense but still parseable.

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?

The output schema means return values needn't be explained, good. But with zero annotations and 0% schema coverage, the description should also identify what 'sender' means and whether setting replaces or appends, leaving the definition adequate but incomplete.

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 0%, so the description must compensate. It explains the 'buttons' parameter well (objects with id/label, plain labels, [] clears), which goes beyond the untyped 'items: {}' schema, but the 'sender' parameter is never mentioned at all.

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 concretely says it manages 'extra buttons on the page' and shows both the data shape and the clearing behavior, so an agent knows what resource it touches. It never states the operation as a verb ('set'/'replace') and doesn't distinguish itself from sibling phone_* tools, so it falls just short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no sibling is named. The clearing behavior ('[] or none clears them') implies usage, but the agent is left to infer the context in which extra phone buttons should be configured.

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