surge_reload_profile

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

The description is minimal and does not disclose what 'reload' entails—whether it applies pending changes, is destructive, or requires prior modifications. With no annotations, the full burden falls on the description, which it fails to meet.

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 concise (one sentence), but it is too brief and lacks valuable detail. While conciseness is valued, the sentence does not earn its place as it fails to inform the agent adequately.

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 simplicity of the tool (no parameters, no output schema), the description could be sufficient, but it lacks context about side effects, expected outcomes, and relationship to sibling tools. The agent cannot determine invocation effects or success criteria.

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?

There are no parameters, and schema coverage is 100% by default. The description adds no parameter information beyond the schema, but the baseline score of 4 for zero-parameter tools 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 clearly states the action ('Reload') and the resource ('the current profile'), making the purpose clear. However, it could be more explicit about what 'profile' refers to and how it differs from the 'surge_get_profile' sibling.

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 is provided on when to use this tool versus alternatives like surge_get_profile or surge_flush_dns. No prerequisites or context for usage are mentioned.

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