load_profile

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

Annotations provide only destructiveHint=false, so the description carries most of the behavioral burden and does so well: it declares idempotency (already-loaded load is a no-op) and a concrete side effect (emitting notifications/tools/list_changed so the client refreshes). It stops short of describing failure behavior for an unknown profile name.

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 purpose is front-loaded in the first sentence, followed by the behavioral caveats and the argument note, with no filler. The multi-line wrapping is slightly awkward but every sentence contributes information.

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 activation tool with a minimal annotation set and no output schema, the description covers purpose, idempotency, and the side effect on the client tool surface. Error handling for an invalid profile name is the only notable omission.

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 100% and the single parameter is documented identically in the schema and the Args block. The description therefore adds nothing beyond the structured field, matching the baseline for full schema coverage.

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?

States a specific action (surface every tool) targeted at a named resource (profile ``name``), which is unambiguous on its own. It does not explicitly contrast with the closely related siblings `unload_profile` and `list_profiles`, so the differentiation is inferable rather than stated.

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?

It points the agent at `list_profiles` to obtain a valid profile name, which is useful routing guidance. However, it never states when to load vs. unload a profile or what precondition must hold, leaving usage context implied.

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