mobileauth_add_biometric

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 only says 'Add', which weakly implies mutation, but does not disclose what files are modified, whether an API key is required, what side effects occur, or whether the operation is reversible.

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 short but this is under-specification rather than effective conciseness. It contains no front-loaded actionable content beyond what the tool name already conveys.

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?

With no annotations, no output schema, only partial parameter documentation, and a vague one-line description, the tool is far from callable by an agent. Critical details about required inputs, behavior, and expected results are entirely missing.

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 only 50%, with 'api_key' entirely undocumented and 'directory' minimally described as 'Project directory'. The description adds no meaning to either parameter, failing to explain how they relate to adding biometric authentication.

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 is essentially a restatement of the tool name: 'Add biometric authentication' adds no new information about what the tool does, what artifacts it touches, or what 'biometric authentication' means in this context. It does not differentiate from sibling tools like mobileauth_generate_flow or mobileauth_add_token_storage.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no context about whether this should follow mobileauth_generate_flow or be used standalone. An agent has no basis for selecting this tool correctly.

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