load_context

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

Lacking annotations, the description must disclose side effects and behavior. It only says 'load context' without explaining whether this modifies state, requires permissions, or what 'compact' means. The presence of a 'budget' parameter suggests resource bounds, but this is not clarified.

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 very concise (one sentence) but lacks structure and essential details. Conciseness should not sacrifice information value.

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 complexity (3 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain return values, how parameters affect behavior, or the tool's role in the overall workflow.

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 needs to explain the parameters. It does not mention 'query', 'budget', or 'preset' at all, leaving the agent to guess their purpose and allowed values.

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 states the action ('load') and the resource ('compact Agentpack context'), clearly indicating what the tool does. It is specific enough to distinguish it from siblings that handle evidence, records, or task lifecycle.

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?

No guidance on when to use this tool versus alternatives like attach_evidence or record_source. The description does not mention scenarios where this tool is appropriate or not.

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