load_outline

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

No annotations are provided, so the description carries the full burden. It describes the return format (path, slide_count, optionally slides) but does not mention error handling, prerequisites, or whether the operation is read-only. This is adequate but leaves some gaps.

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 clear but includes a docstring-style Args section that largely repeats the schema, making it slightly longer than necessary. The first sentence is efficient, but the rest could be condensed.

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?

Given the simple parameters and existence of an output schema, the description covers the main functionality and return values well. It could briefly mention error cases, but overall it is sufficiently complete for a straightforward loader.

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?

With 0% schema description coverage, the description compensates well by explaining include_content's behavior (returns full content if True, else only path and count) and its default value, adding meaning beyond the schema's minimal titles.

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 clearly states the tool loads a saved outline JSON from the project directory, and mentions its use as input for downstream tools like prepare_design_slide and export_html, distinguishing it from siblings like prepare_outline or save_outline_slide.

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?

It provides explicit context for when to use the tool by stating the loaded result can be used as input for other tools, but does not explicitly compare to alternatives like capture_slides or mention when not to use it.

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