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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that the payload is booleans and carries no user data; it says nothing about where the data goes, whether repeated reports merge or overwrite, or what is returned.

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?

One sentence, front-loaded with the caller restriction and the verb, with the payload constraint trailing. Nothing is padded.

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 19-parameter telemetry tool with no output schema and no enum or description coverage, the description answers who calls it but not what the flags mean or what a call produces. That leaves the agent unable to populate the payload meaningfully.

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% and there are 19 flags, many highly cryptic (rtc_srflx, direct_ok, render_local, ended_on_close, wss_blocked). The description supplies no per-parameter meaning at all, and 'booleans' merely restates the schema's type declarations, so an agent cannot tell what any individual flag asserts.

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 gives a specific verb and resource: 'records which display modes and browser features the host allows.' The parenthetical '(booleans, no user data)' narrows the payload, and the 'bitHuman widget only' clause separates it from the sibling character/video tools.

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?

'Used by the bitHuman widget only' is an explicit caller restriction, effectively telling the agent when not to use it. It does not name a specific alternative, but the exclusivity clause makes the routing decision unambiguous.

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