set_parameter

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

No annotations are provided, so the description carries the full burden of disclosing behavior. 'Modify State Parameter' gives no insight into side effects, persistence, error handling, return values, or permission requirements. It is a mutation tool whose behavior is completely opaque.

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 one short sentence, but it is under-specified rather than concise. It omits essential operational details and does not earn its place because it adds negligible value beyond the tool's name.

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 simple but critical setter tool with 2 parameters, no annotations, no output schema, and no parameter documentation, this description is completely inadequate. It fails to provide any context about state, parameter paths, value ranges, or expected effects, making correct invocation nearly impossible.

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 defines 'path' (string) and 'value' (number) but offers no descriptions, and the description adds no meaning to these parameters. With 0% schema coverage and no parameter explanation, an agent cannot know what path should look like or how value should be interpreted.

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 'Modify State Parameter' essentially restates the tool name 'set_parameter' with a vague qualifier, providing no specific verb+resource combination or details about which state or parameter. It does not distinguish this tool from many sibling state-related tools (e.g., get_snn_state, wm_*).

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?

There is no guidance on when to use this tool versus alternatives. The description only states the tool's generic action without any context, prerequisites, or exclusions, leaving the agent without decision-relevant information.

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