load_snapshot

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

Describes key behavioral traits: fast reload, no re-elaboration unless intent=True. No annotations provided, so description carries full burden and adds value beyond schema.

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 concise sentences, front-loaded with primary purpose, no redundant information.

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?

Adequately covers tool behavior and parameter effects, but lacks prerequisites (e.g., snapshot must exist) and return value info.

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?

Explains the intent parameter's effect (re-elaborate warm intent layer) beyond schema; directory parameter is self-explanatory from context. Schema coverage is 0%, so description compensates well.

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 'Reload a save_snapshot directory in seconds (no re-elaboration)' with a specific verb and resource, and distinguishes from siblings by highlighting speed and lack of full re-elaboration.

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?

Clear context for when to use (reload snapshot) and behavior of intent parameter, but does not explicitly state when not to use or mention alternatives like load_intent.

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