Get the raw compile log

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

The description says 'Return' which implies a read-only operation, but the annotation readOnlyHint=false contradicts this by indicating the tool may have side effects. The idempotentHint=true also suggests no side effects, but the readOnlyHint=false directly conflicts with the description's implication. The description does not disclose any behavioral traits beyond the contradiction, so it fails to provide clarity.

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 two sentences with no filler. The primary action is front-loaded, and the usage condition is concise. Every word serves a purpose.

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 simple tool with one parameter and no output schema, the description is almost complete but is undermined by the annotation contradiction. The user cannot trust the read-only implication, and there is no mention of what happens if the compile log is not available or whether it returns the latest log. The contradiction creates a significant gap in understanding.

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%, and the description does not explain the meaning or format of the sole parameter projectId. It only says 'from a compile,' which hints that projectId identifies the project but does not clarify how to obtain or use it. No additional value is added 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 states a specific verb ('Return') and resource ('full raw LaTeX log from a compile'), which clearly distinguishes it from siblings like get_pdf (returns PDF) and read_file (reads arbitrary files). It does not explicitly name a sibling, but the intent is 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?

The description provides a clear usage condition: 'Use when structured diagnostics are insufficient.' This implies a threshold for when this tool is appropriate and suggests an alternative (structured diagnostics), even though that alternative is not named among the siblings. It does not explicitly state when not to use it, but the condition is actionable.

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