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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether names must be unique, whether creation is repeatable/idempotent, what happens on duplicate names, or what the caller gets back.

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 zero filler, which is structurally sound. However, brevity here borders on under-specification for a tool that has real unknowns (naming rules, permissions, return value), so it earns only a middling score.

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 2-parameter mutation with no output schema, the description leaves the agent without naming constraints, permission requirements, duplicate-handling behavior, or any indication of the created folder's identifier. Annotations cover only the generic write-safety profile, so the gaps remain.

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 only 50% — companyId is documented inline (including the active/pinned company default) but name has no description at all. The description mentions "company" only obliquely and says nothing about the name parameter's constraints or the 1–60 character limit, so it does not compensate for the coverage gap.

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 ("Create a QR folder") plus its scope ("in a company"), which is enough to separate it from folders_delete, folders_rename, and folders_list. It does not explicitly name those siblings or state how it differs from them, so it stops short of a 5.

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 when-to-use guidance, no prerequisites (e.g. permissions or plan requirements), and no reference to alternatives such as folders_rename or nesting under an existing folder. The agent must infer everything from the one-line purpose.

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