compile_with_outputs

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is largely covered. The description usefully enumerates the output artifact types returned, but says nothing about compile failure behavior, timeouts, or whether artifacts persist server-side — relevant since compilation does produce files.

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?

Two short sentences with no filler, and the core action plus return scope is front-loaded. The trailing "Useful for arXiv submission workflows" is the only sentence that borders on optional, though it does carry the usage hint.

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?

No output schema exists, and the description partially compensates by listing returned artifact types. It omits error/failure semantics for a compile operation and any indication of latency or async behavior, leaving meaningful gaps for an agent to fill.

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%, and both parameters (project_id, resource_path) are documented in the schema with examples. The description adds no parameter-level detail, which is acceptable at full coverage but earns only the baseline.

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 and resource ("Compile an Overleaf project") and adds a distinguishing outcome ("return all output file metadata (PDF, BBL, logs, etc.)"). It never names the sibling `compile` or `download_pdf`, so the agent must infer how this differs from a plain compile, but the return-scope detail does most of the differentiating work.

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?

"Useful for arXiv submission workflows" implies a usage context (you need BBL/logs alongside the PDF), but it gives no explicit when-not condition and does not name `compile` or `download_pdf` as alternatives. The agent is left to infer the selection rule from the mention of extra output types.

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