load_brief

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

Discloses a key behavioral trait: returns an empty skeleton if no brief exists, and implies state persistence. With no annotations provided, the description carries the burden and does so adequately, though it doesn't mention side effects or authentication.

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 sentences with no wasted words, front-loading the main action and the key behavior. The structure is efficient and easy to parse.

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?

Covers usage context and the empty skeleton case, and the output schema handles return format. However, the lack of parameter explanations means the tool is not fully usable without external knowledge, making it only partially complete.

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?

The description adds no information about the 'study' or 'work_dir' parameters. With schema description coverage at 0%, the agent gets no guidance on what values to pass, leaving a significant gap.

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 action ('Load a study brief') and the resource (a brief), and adds the nuance of returning an empty skeleton when none exists. This makes it unambiguous and distinct from the sibling 'save_brief'.

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?

Explicitly instructs to call at journey start to resume where left off, providing clear when-to-use guidance. It also implies the behavior when no brief exists, which helps the agent decide to call it.

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