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

With no annotations, the description carries full burden. It only adds 'Browser-based tool', which implies some rendering context, but does not disclose how input is provided, output format details, limitations, or any side effects. This is a minimal gesture toward transparency.

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 one short sentence, front-loaded with the core function, and includes no filler or redundant content. It is appropriately sized for a zero-parameter tool.

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?

Despite being a simple tool, the description omits essential context: how HTML content is supplied, what the output PDF contains, and any browser-specific behavior. Given the abundance of sibling PDF tools and the lack of output schema/annotations, this description is incomplete.

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 has zero parameters, so the baseline score is 4. The description does not need to explain parameter details since none exist, and the schema coverage is trivially 100%. No conflict arises.

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 specific verb and resource: 'HTMLをPDFに変換' (convert HTML to PDF). This clearly distinguishes it from sibling tools like excel-to-pdf, word-to-pdf, and image-to-pdf, making the purpose 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?

The description provides no guidance on when to use this tool versus alternatives such as other conversion tools. It only mentions 'Browser-based tool', which hints at context but does not offer exclusions or alternative suggestions.

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