simulate_biometrics

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

No annotations are provided, so the description carries the full burden. It discloses the two possible outcomes (success or failure) via the match parameter, but doesn't describe whether this blocks, requires an active app, or any side effects. For a simulation tool with an output schema, the description adds some value but leaves behavioral gaps.

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?

A single, front-loaded sentence that states the action and the controlled outcome. No wasted words.

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 the presence of an output schema, the description needn't explain return values, and it covers the core action and the outcome parameter. However, without annotations, it could be improved by noting prerequisites (e.g., simulator must be booted) or typical use case, but it is largely complete for a simple simulation tool.

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 100%, so the schema already fully documents both parameters (match and device_id). The description mentions success or failure but doesn't add syntax or format details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (simulate) and resource (Touch ID or Face ID authentication), and clarifies scope with success/failure. It clearly distinguishes itself from other simulator controls like tap or press_button.

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 (to simulate biometric authentication during testing) but gives no explicit when-to-use conditions, prerequisites, or alternatives. With many sibling tools, some guidance on when biometric simulation is relevant would help, but it's not strictly required for this focused utility.

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