load_capsule

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Load a saved experiment capsule by ID' and does not explain what loading does to the current workspace, whether it replaces the active model, whether it requires an active connection, or what state changes occur.

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 a single, front-loaded sentence with no filler or redundancy. It is concise and easily parsed, though the brevity contributes to missing behavioral and usage guidance.

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?

For a one-parameter tool with an output schema, the core call is inferable: provide capsule_id. However, the lack of annotations and the absence of any statement about side effects or workspace impact leave meaningful gaps for an agent choosing among many capsule-related tools.

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 0%, so the description must compensate for the bare schema. 'By ID' tells the agent that capsule_id is the saved capsule identifier, but it does not clarify expected ID format, where to find valid IDs, or how this relates to list_capsules. The added meaning is minimal.

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 uses a specific verb ('Load'), a specific resource ('saved experiment capsule'), and a criterion ('by ID'). This clearly distinguishes it from siblings like create_capsule, list_capsules, delete_capsule, and compare_capsules.

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 context implies use when an agent has a capsule ID and needs to work with an already saved experiment, but it does not explicitly state when to prefer this over list_capsules, create_capsule, or other alternatives. No exclusions or alternative routing are provided.

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