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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior; the description adds useful behavioral context: org ownership constraint, null clearing, and write-tier classification. It does not add permission details or return behavior, but the annotation coverage lowers the burden.

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?

Front-loads the core action and mode distinctions in one dense sentence, then adds two short constraints. Parenthetical endpoint details are compact and no sentence is wasted.

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?

Covers both operational modes, clearing behavior, org ownership, and write-tier semantics for a tool with no output schema. Some schema gaps remain around conditional requiredness and return behavior, but the description is substantially complete.

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?

With 0% schema description coverage, the description compensates well by explaining qr_style_id null-clears, target+id for item assignment, and target purpose with purpose values. It still leaves id requiredness for non-purpose targets and exact purpose enum values implicit.

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: applying a saved QR look, with explicit distinction between item-level application and purpose-level defaulting. It also names the relevant targets, so the agent can distinguish it from save_qr_style, list_qr_styles, and generate_qr.

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?

Gives clear usage contexts: project/list/task/site with id, or purpose with purpose values. It does not explicitly compare with sibling tools or state exclusions, but the target-based routing is concrete enough for correct selection.

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