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

Annotations already flag readOnly=false, destructive=true, openWorld=true. The description adds genuinely new lifecycle behavior: default one-hour expiry, 24-hour maximum, and that the source is removed on completion or expiry. This is useful beyond the annotations, though it omits why it is destructive or how operationID/controlToken govern auth.

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?

Four short front-loaded sentences with no filler; the core async/expiry behavior leads. Efficient, though terse enough that it leaves major schema gaps unaddressed.

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 11-parameter, 7-required mutation with no output schema and 9% schema coverage, the description covers the queuing model and expiry but not the meaning of key tokens or the create/update action shape. Adequate for the lifecycle story, incomplete for correct invocation.

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 9% across 11 parameters, so the description must compensate and largely fails. It hints at expiry (expiresInSeconds) and source removal, but operationID, controlToken, expectedRevision, action, format, data, state, componentID and title receive no semantic explanation anywhere.

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 and resource with distinguishing scope: it queues a component create/update for a background or offline browser and returns 'queued rather than rendered'. This clearly separates it from synchronous create_component/update_component, though it never names those siblings explicitly.

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 phrase 'background or offline browser' and 'returns queued rather than rendered' imply when this async path is chosen, but there is no explicit when-to-use/when-not or named alternative (create_component, update_component). Usage must be inferred from context.

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