render

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

No annotations are present, so the description must convey behavioral traits. It discloses return values for each action (PDF path, file path/dimensions, LaTeX content) but omits potential side effects (e.g., file overwriting, permission requirements) or dependencies on prior document state.

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 concise, front-loading the overall purpose and using a clear bulleted list for each action. Every sentence adds value with no redundancy.

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 tool's multiple actions and lack of annotations, the description covers return values but not parameter usage or contextual dependencies. The presence of an output schema (not shown) may mitigate completeness needs, but gaps remain in parameter semantics and behavioral context.

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?

Schema description coverage is 0%, leaving the description to explain parameters. It does not explicitly map parameters (output_path, page, dpi) to actions; the action names hint at their use but lack explicit constraints or format details beyond the schema.

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 the tool's purpose: 'Compile and export the document', and enumerates three specific actions (compile, preview, tex) with distinct functionalities. It differentiates well from sibling tools (e.g., document, edit) that handle other aspects of document management.

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 implies usage through action descriptions but does not explicitly state when to use this tool versus alternatives or exclude scenarios. No guidance on prerequisites or conflict with other tools is provided.

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