helpers_set_input_number

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

With no annotations, the description must disclose behavior. 'Set' implies mutation but does not state if it's idempotent, what happens if the entity doesn't exist, whether there are constraints on the value, or what the response looks like. This is insufficient 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 very concise (4 words) and front-loaded, which is good. However, it may be too terse, sacrificing clarity for brevity. It earns a middle score because conciseness is positive but it lacks necessary detail.

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?

The tool is simple (2 parameters) but the description is too minimal given no schema descriptions and no annotations. It does not cover the nature of the value, error handling, or return values (though an output schema exists). The description is incomplete for safe and correct usage.

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 0% and the description adds no parameter details. The schema defines 'entity_id' and 'value' but the description does not explain their meaning, restrictions, or expected format. Given the low coverage, the description should compensate but does not.

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 ('Set') and the resource ('an input_number value'), which distinguishes it from sibling tools for other input types like input_boolean or input_datetime. However, it could be more specific about the nature of the value, but overall it's clear.

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 vs alternatives. Sibling tools exist for other input types (e.g., helpers_set_input_boolean), but the description does not help the agent choose between them based on entity type or scenario.

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