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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return modality (JSON) but says nothing about behavior on malformed QTML — whether it errors, returns a partial tree, or embeds diagnostics — which is the main unknown for a parser.

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?

Two short sentences with zero filler; the operation and output format are front-loaded and the second sentence adds the usage cue.

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 simple read-only single-argument parser with full schema coverage and no output schema, the definition covers what and when adequately. The only meaningful omission is error/failure behavior on invalid input, which an agent would want to know before calling.

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 both parameters are fully documented in the schema, and the description merely restates the 'source' meaning. The required 'context' analytics parameter is not mentioned at all in the description, but the schema handles it, so baseline 3 applies.

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: parse a QTML source string, returning a structured JSON representation. This distinguishes it operationally from convert_qtml_to_playwright and validate_qtml, 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?

'Use this to inspect the contents of a QTML document' implies a read/inspection use case but gives no when-not guidance, no mention of validate_qtml as the alternative when the goal is checking correctness, and no prerequisites about where the QTML string comes from.

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