load_tools

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it emits notifications/tools/list_changed, returns the loaded tools' schemas, and explains that the tools are usable even if the client ignores the notification (via batch). It also discloses the response JSON shape (loaded, already_loaded, unknown, blocked, tools, hint), which is not otherwise specified.

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, tightly packed with essential information, and the core action is front-loaded. Every clause adds value: the loading modes, the no-args list behavior, the notification side-effect, the batch fallback, and the return format. No redundancy or fluff.

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 a simple 2-parameter schema with no output schema, the description is remarkably complete. It explains the exact behavior, the notification, the return shape (including fields like 'unknown' and 'blocked'), and how to use the returned tools through batch. There is no missing information an agent would need to invoke this tool correctly.

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 coverage is 100% for both parameters (preset and tools), so the schema already describes each parameter adequately. The description adds minimal parameter-specific meaning beyond the schema—only the hint to call with no arguments to list deferred tools, which is more usage guidance than parameter semantics. Baseline 3 is appropriate.

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 a specific verb ('Load') and resource ('this session's preset deferred'), and clarifies the two modes (preset and/or explicit tool names, or no args to list). It is clearly distinct from sibling tools like get_preset_info and batch, so an agent can immediately tell which tool to invoke.

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?

Provides explicit usage context: call with no arguments to list deferred tools, and use the `batch` tool to call the loaded tools (since schemas are returned). It does not explicitly list when not to use this tool or name alternatives, but the batch reference and the 'list' mode give sufficient guidance for typical use cases.

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