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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that it auto-generates patterns and prevents firestorms, and notes it is browser-based, but it does not explain how the tool behaves, what output to expect, or any limitations. This is thin for a tool with no structured safety metadata.

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 very concise and front-loaded, with no filler. The parenthetical '(Browser-based tool)' and the benefit clause '炎上防止' are useful but not strictly operational, so it earns a 4 rather than a 5.

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 zero-parameter, browser-based tool, the description is mostly complete: it states the input domain (reviews), the output type (reply patterns), and the intended benefit. It lacks explicit details about output format or how to proceed after generation, but given the tool's simplicity, it is adequate.

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 tool has zero parameters, and the schema coverage is 100% (empty schema). The description adds context about the tool's purpose and output, but there are no parameter semantics to explain. Baseline 4 is appropriate given no parameters exist.

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 clearly states a specific action: automatically generating reply patterns for high/low ratings. The benefit '炎上防止' (firestorm prevention) adds useful context, and the tool is clearly differentiated from sibling content-generation tools by its focus on review replies.

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?

Usage is implied: use it when needing reply templates for reviews, especially to avoid controversy. However, it does not explicitly mention when to prefer this over alternatives, nor does it state any exclusions or prerequisites.

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