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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'Pure computation, free' corroborates that this is side-effect-free with no cost. Beyond that it adds nothing about output shape or the effect of the mode switch.

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, front-loaded with the action and followed by an operational note. No wasted words.

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 two-param tool this is close, but the undefined 'mode' parameter is a genuine gap given 0% schema coverage and no output schema, and it determines which of the two advertised operations actually runs.

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 0%, so nothing documents the two parameters. The description never mentions the 'mode' parameter at all, leaving the agent to guess its accepted values (escape vs unescape) and whether it is required or has a default.

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 (escape/unescape) and resource (HTML special characters), which is clear and distinct from siblings like bursia_url_encode or bursia_base64. It doesn't explicitly contrast with those siblings, but the resource scope is unambiguous.

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?

Provides no guidance on when to choose this over bursia_url_encode or other encoding siblings, and does not say when to escape versus unescape. Only the ambient 'free' note hints at usage context.

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