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

With no annotations, the description carries the full behavioral burden. It discloses the return shape (page + x/y + width/height) and the compile prerequisite, which is useful. It does not cover failure modes (unsynced line, missing file) or permission needs, so coverage is adequate but not complete.

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 tight sentences with no waste; the core purpose and return value are front-loaded, and the prerequisite trails as a short caveat. Every sentence earns its place.

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?

An output schema exists, so the return-format mention is a bonus rather than a necessity, and the compile prerequisite is helpful. But for a 5-parameter tool with 0% schema coverage, the description omits context on column, pdf_filename, and project_id, leaving the calling contract under-specified.

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% across 5 parameters, so the description must compensate, and it only implies 'file' and 'line'. It says nothing about 'column' (optional), 'pdf_filename' (defaults to output.pdf), or 'project_id', leaving three parameters undocumented anywhere.

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?

States a specific verb ('Resolve') and resource ('source file/line to the PDF highlight rectangle'), and the '(source → PDF)' directional marker effectively distinguishes it from the synctex_backward sibling without needing to name it. An agent can tell the two apart at a glance.

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?

Provides one concrete prerequisite ('Requires a prior compile'), which is genuine usage context. However, it never names synctex_backward or states when to pick this direction over the reverse, leaving alternative selection to inference from the arrow notation.

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