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

No annotations are provided, so the description carries full behavioral disclosure burden. It only adds 'Browser-based tool', hinting at local browser processing, but it omits important traits such as camera permission requirements, whether images are uploaded to a server, or how the resulting PDF is delivered. A camera-accessing tool needs more 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 compact sentence plus a parenthetical note, with no filler. It communicates the core function and browser context efficiently. Every element earns its place.

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?

Tool complexity is low with no parameters, no output schema, and no annotations, so the description need not be extensive. However, it does not state what the user receives (e.g., a downloadable PDF) or any caveats about camera use. The 'Browser-based tool' note adds some context but leaves the basic outcome unspecified.

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 is 4. The description adds no parameter-specific details, but none are needed since the schema is empty and fully covered. This is appropriate for a no-parameter tool.

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 uses a specific verb phrase 'カメラで撮影してPDF化' (photograph with camera and convert to PDF), clearly stating the tool's function and resource. It distinguishes scan-pdf from sibling tools like image-to-pdf by emphasizing live camera capture rather than existing image files.

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 camera-based workflow implies the tool is for scanning physical documents, but no explicit when-to-use or alternative guidance is provided. The description does not mention when this tool should be preferred over related PDF/image tools. Usage context is implied rather than stated.

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