Read the last compile's output.log

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

The description discloses detailed behavioral traits: the `content` array shows a summary of `!`-prefixed error lines at the top, and the log is truncated to the last 8000 chars for display, while `structuredContent.log` contains the full untruncated log. This goes beyond the readOnlyHint annotation and explains exactly what callers can expect.

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 three sentences, each earning its place: the first states the core purpose, the second provides usage guidance, and the third details the response format. It is front-loaded and free of 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?

Given the tool has no parameters and no output schema, the description fully compensates by explaining both the display content and the full structured content. It addresses how the tool differs from `compile` and what the caller can parse. This is complete for a zero-parameter, read-only logging tool.

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 the schema coverage is 100% as there are no properties. The description does not need to explain parameter semantics, but it enriches understanding by explaining the response structure. Baseline for zero parameters is 4, and this description meets that.

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 returns the full LaTeX log from the most recent compile call, with a specific verb ('Returns') and resource ('full LaTeX log'). It distinguishes itself from the sibling `compile` tool by noting that `compile` already provides error count and first few errors, making this tool's purpose clear and complementary.

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 explicitly states when to use this tool: 'use this only when you need more context (full log, line numbers, package warnings, etc.)' and contrasts it with `compile`, which includes error count and first few errors. This provides clear usage guidance and indirectly names an alternative.

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