load_tools

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

The description discloses behavior beyond the annotations: it emits notifications/tools/list_changed, returns loaded tools' schemas, and remains usable even if the client ignores the notification (via batch). It also lists the exact JSON response fields, giving the agent a clear model of side effects and results.

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 dense but efficient: it front-loads the core purpose, then covers invocation modes, side effects, and return shape in a few sentences. No sentence is filler, and the structure makes the most important information immediately visible.

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?

Despite having no output schema, the description names all return fields and explains the notification behavior and batch fallback. Combined with the annotations signaling read-only/idempotent behavior, the description gives the agent enough context to invoke the tool correctly and interpret its response.

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 input schema already describes both parameters with 100% coverage, including the union behavior between `tools` and `preset`. The description adds value by specifying the no-arguments listing behavior, which is a parameter-level semantic not captured by the schema alone.

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') with a clear resource: deferred tools for the session's preset, by preset name and/or explicit names. It also distinguishes the no-argument listing mode, making the tool's purpose unambiguous and distinct from siblings like get_preset_info.

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 description gives clear usage context: call with no arguments to list deferred tools, or pass preset/tool names to load them. It does not explicitly mention alternatives or when-not-to-use conditions, but the provided context is sufficient for typical invocation.

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