encode_html_entities

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

The description does not disclose any behavioral traits beyond what is implied by the name and annotations. Annotations set readOnlyHint to false, which is consistent with a transformation tool, but no additional details about side effects, performance, or limitations are provided.

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?

The description is a single short phrase, which is concise but lacks structure. It could benefit from being slightly more descriptive without becoming verbose, but it is not overly concise to the point of being unclear.

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?

The description fails to mention what the tool returns, especially since there is no output schema. It also does not provide examples or context about entity coverage, leaving gaps in understanding for an AI agent.

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?

The input schema already covers 100% of parameter descriptions, so the description adds no extra semantic value. Baseline score of 3 is appropriate as the schema does the work.

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 'Extended HTML entity encoding/decoding' clearly states it handles both encoding and decoding, using a specific verb and resource. However, it does not distinguish itself from sibling tools like encode_html or decode_html, which also perform encoding/decoding.

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?

No guidance is provided on when to use this tool instead of alternatives like encode_html or decode_html. The term 'Extended' hints at broader entity coverage, but without explicit context, the agent cannot differentiate usage scenarios.

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