infra_configure

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

Discloses that changes are immediate and affect subsequent calls. Annotations already indicate idempotentHint=true, so no contradiction. Could elaborate on when auth_token is required, but overall adds value.

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 front-loaded purpose. Every word is informative; no unnecessary content.

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?

Adequate for a configuration tool with good annotations and output schema. Minor gaps: interaction between preset and model is not explained, and auth_token requirement is implicit.

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%, so baseline is 3. The description merely lists the parameter categories without adding extra meaning beyond schema. No new semantics introduced.

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?

Description clearly specifies the verb 'Reconfigure' and resource 'server', listing the configurable aspects (preset, model, thinking level, temperature). It effectively differentiates from sibling tools by being the sole configuration tool.

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?

States that changes take effect immediately, providing clear context for when to use. Does not explicitly mention when not to use or alternatives, but the unique role makes usage clear.

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