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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'Runs in the browser' and credit coverage, but does not disclose side effects, data handling, file size limits, or output format specifics. This is insufficient for a tool with no annotation support.

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 first sentence is front-loaded and clear, but the remaining sentences about credits and workspace groups are verbose and not essential for invoking the tool. The description could be shortened to focus on the conversion task, making it more concise.

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?

Given the lack of output schema and annotations, the description should provide more context about input/output expectations. It does not explain how to provide a TIFF file or what the returned PDF looks like. Even though the tool is simple, the description's focus on billing leaves a gap in operational completeness.

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 schema coverage is 100% (trivially). With 0 params, the baseline is 4, and the description does not need to explain parameter semantics. It doesn't, which is appropriate.

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 explicitly states 'Convert TIFF images to PDF documents', which is a specific verb+resource action. It also distinguishes itself from sibling tools (e.g., png_to_pdf, jpg_to_pdf) by naming the TIFF format, making its 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?

There is no explicit guidance on when to use this tool versus alternatives, but the purpose implies usage for TIFF-to-PDF conversion. The description instead devotes space to credit/workspace details, which is not directly about usage context. No exclusions or alternative tools are mentioned.

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