open_project

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

With no annotations, the description carries the full burden, and it does substantive work: it discloses side effects (parsing sentences/citations/bibliography, restoring prior verdicts) and specifies the returned overview (language, counts, missing .bib keys). It does not state performance cost, failure modes, or whether restored verdicts can be reset, which keeps it from a 5.

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 efficient sentences, front-loaded with the core verb and the re-open condition. Every clause carries information (behavior plus return shape). Minor density in the middle sentence keeps it just below maximal.

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, so the description correctly describes the return value (language, counts, missing .bib keys), and it explains the side effects of loading. Combined with full schema coverage, an agent has enough to invoke it, though it lacks any note on dependencies with sibling tools that consume the opened project.

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%, so all three parameters (bib, pdf_dirs, manuscript) are already documented in the schema, including that \input/\include files are followed. The description adds no parameter-level detail beyond this, so the baseline of 3 applies.

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 and resource ('Open ... a manuscript') and enumerates the concrete work done: parsing sentences, citations, bibliography, and restoring previous verdicts. This clearly positions it as the session/entry-point loader, distinct from read_source, verify_quote, or check_bibliography. It could be sharper by explicitly naming a sibling it is not, but the purpose 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 parenthetical '(or re-open after edits)' implies a when-to-use condition, but there is no explicit statement of alternatives, prerequisites, or when-not to call it (e.g., whether it must precede verify_quote/record_verdict). Guidance is implied rather than spelled out.

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