functions

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

Beyond the annotations, the description discloses important behavior: it works while the phone is locked, reading is free, creating/updating changes user data, destructive actions require confirm=true, calls require confirm plus an exact accord, missing fields produce app errors naming the field, and outputs are data with sensitive tokens masked.

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 definition is dense but front-loaded: it states the purpose first, then list/run behavior, then safety/confirmation rules. Most clauses earn their place, though the long semicolon-heavy paragraph could be more structured for scanning.

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 complex, open-world dispatcher with no output schema, it covers the key call patterns, confirmation requirements, error behavior, and output masking. Return shape remains vague beyond 'Answer = data', and sibling differentiation is absent, but the agent has enough to invoke list and run correctly in most cases.

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?

With 0% schema description coverage, the description does compensate for app, function, params, confirm, and accord usage, including an example params object. But accord is only vaguely described as 'the accord for this exact call' without saying where it comes from or its format, and the action parameter is only implied through list/run examples.

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 defines the tool as a dispatcher for Android AppFunctions, with explicit list and run modes and concrete app-domain examples. However, it does not contrast itself with sibling tools such as launch, messages, phone, or apps, leaving the agent to infer when this general dispatcher is preferable.

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?

It gives clear operational guidance: use list to discover apps/functions, use run with app/function/params, and set confirm=true for destructive actions and calls plus an accord for calls. It does not explicitly say when to avoid this tool or which sibling tool to use instead.

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