load_plan

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

In absence of annotations, description fully discloses that the session is replaced (clears previous document, scales, etc.) and explains the coordinate system in detail, including origin and scaling. No contradictions.

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?

Description is concise and well-structured, front-loading the main action and side effect, then listing return values and coordinate details efficiently.

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?

With only one parameter and no output schema, the description adequately details return structure and coordinate system, leaving no critical gaps.

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 has 100% coverage with good description for 'path'. The tool description merely reinforces the parameter's role without adding new semantics 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?

Description clearly states it opens a PDF and replaces the entire session, specifying return values like file, page_count, and per-sheet data. No ambiguity with sibling tools, which are all different.

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?

Description implies usage when loading a new plan but does not explicitly state when not to use or alternatives. However, sibling tools are distinctly different, so context is clear.

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