Read one LaTeX section

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

Annotations only give readOnlyHint/openWorldHint; the description adds substantial behavior: source resolution (Overleaf first), an explicit output cap of 60,000 characters with truncation, the boundary rule that stops before \appendix/bibliography/\end{document}, and the failure mode of returning existing titles. That is a lot of operational context beyond the annotations.

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?

Front-loaded with the core action and free of filler, but it is dense: matching rules, truncation limit, source precedence and fallback behavior are packed into a few long multi-clause sentences, which would read better split out.

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?

There is no output schema, and the description compensates fully: it says what is returned (the section's stored LaTeX, truncated at 60,000 chars) and what happens on no match. Combined with the boundary and source rules, an agent has everything needed to call this correctly.

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 coverage is 100%, yet the description goes past it by explaining that sectionTitle is matched case-insensitively against the brace title (not the [short] title), with exact match winning and otherwise first-containing match in document order — plus the concrete consequence that a short fragment may resolve to an earlier section. This is real added meaning for a required parameter.

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?

Opens with a precise verb+resource+scope: 'Read one section of a .tex file by its title', then defines the exact boundary (heading to next heading at same or shallower level). It explicitly contrasts itself with read_file, so an agent can separate it from sibling tools without opening any 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?

States the positive trigger ('when revising one part of a paper, so the rest stays out of context') and names the alternative to avoid ('Prefer it over read_file'). It also points to list_sections as the disambiguation step and records the 'Pulls from Overleaf first' source precedence.

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