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

Adds real behavioral context beyond the thin annotations: sandboxing ("no shell escape"), the TeX distribution and its limits ("TeX Live with common packages"), failure behavior ("the error lines if it fails"), and a per-call price with payment protocol ("$0.008 USDC per call (x402)"). It leaves compilation timeout/failure-recovery detail implicit, but the security and cost disclosures are exactly the kind of thing annotations do not convey.

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?

Three sentences, front-loaded with the action and engine, then the calling contract, then the cost. Every clause carries information (engines, packages, sandbox, input files, output, failure mode, price) with no filler.

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 5-parameter, no-output-schema tool the description covers inputs (source, images, .bib), output (PDF or error lines), and cost. Minor gaps remain around return encoding (base64 vs share link) and size limits, which the schema partially handles via store/format but the description does not tie together.

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 100%, so the engine/store/format/source semantics are already documented structurally; the description only echoes the engine options and file types. Baseline 3 applies when the schema carries the parameter burden.

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?

Specific verb+resource ("Compile LaTeX to PDF") with the engines named inline, which immediately separates it from siblings like pdf, pdf_tools, doc_convert, or office_convert. An agent can tell exactly what this tool produces without opening the schema.

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?

"Send the full source plus any image or .bib files" tells the agent what input shape is expected and when the tool is applicable (LaTeX sources only). It does not, however, name a sibling alternative or state exclusions such as size limits or unsupported package classes, so it stops short of full when/when-not routing.

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