revert_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 behavioral disclosure. It only states that the parameter is reverted to default, but does not mention side effects (e.g., removing expressions or overrides), permissions required, whether the operation is reversible, or what happens if the parameter is already at default. This is an incomplete disclosure for a mutation tool.

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 extremely short and front-loaded. It contains only a clear action sentence and a minimal parameter list, with no unnecessary words. It earns its place by being immediately scannable.

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?

Although the tool is simple (two params, no output schema), the description lacks essential context such as the expected format for node_path, the meaning of 'revert' in Houdini (e.g., resetting to built-in default vs. clearing expressions), and any error conditions. An agent without prior Houdini knowledge would likely be uncertain how to correctly invoke it.

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 schema has zero description coverage (only titles), so the description must compensate for the missing parameter information. The Args section merely repeats the parameter names ('Node path.', 'Parameter name.') without adding formats, examples, or constraints. This adds little beyond the schema titles and fails to tell the agent what a valid node_path or parm_name looks like.

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 a specific verb ('revert') and the resource ('parameter to its default value'), which is distinct from sibling tools like set_parameter or get_parameter. It unambiguously tells the agent what action is performed.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It implies usage solely through the action word 'revert', but does not explicitly mention, for example, that it should be used instead of set_parameter when a reset to default is desired.

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