type

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

Annotations already flag destructiveHint=true, so the agent knows this mutates state. The description adds no behavioral context: it does not mention that the default clear=true overwrites existing content, nor explain permissions, targeting requirements, or failure behavior.

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 with no filler. It is well-sized for a one-line tool, though its brevity reflects under-specification rather than efficient density.

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 7-parameter mutation tool with 14% schema coverage and no output schema, the description is far too thin. It omits the targeting hierarchy, the destructive clear default, and any return/confirmation behavior an agent needs to call it correctly.

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 14% (only targetId is documented) across 7 parameters, so the description must compensate but does not. It never explains ref, selector, index, snapshotId, or the significance of the clear default, leaving most parameters semantically opaque.

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 ('Enter text into a selected Typora element') and names the mechanism ('through Playwright/CDP'), which separates it from siblings like click or press_key. However, 'selected element' is left undefined, so the targeting model is not fully clear.

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 statement of when to use this tool versus alternatives such as click, press_key, or the various targeting helpers. Nothing explains how to select/populate an element or when this is preferred over other input tools.

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