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

The annotations already indicate a read-only, idempotent, non-destructive tool. The description adds useful behavioral context: output is grouped by category, can be filtered, and is returned in copyable form. It also cites the source URL. No contradiction with annotations.

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 sentences with no filler: purpose, category list, filtering behavior, output promise, and source are all packed efficiently. The most important information is front-loaded.

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 read-only, single-optional-parameter tool with an output schema, the description is complete: it identifies the content, the grouping, the optional filter, and the copy-ready result. The minor category-name mismatch is resolved by the schema enum.

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 single optional parameter is fully covered by the input schema, including its enum values and default behavior, so the baseline is 3. The description repeats the filtering concept and gives friendlier category names, but 'stars and hearts' and 'legal marks' do not exactly match the schema's enum values, so it adds limited precise meaning.

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 states a clear verb and resource: it 'List[s] special characters and symbols' grouped by named categories, and it explains the result is 'ready to copy.' This clearly distinguishes it from the many calculator/convertor siblings and from more inspection-oriented tools like unicode_inspector.

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?

The description makes the intended usage obvious: retrieve special characters for copying, optionally filtered by category via the group parameter. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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