td_set

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

With no annotations, the description carries the behavioral burden. It discloses accepted value forms and that unknown names return close-matches, but it does not mention side effects, permissions, or connection requirements.

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 three short, front-loaded sentences. Every sentence adds value: purpose, accepted value syntax, and error behavior. No filler or repetition.

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 description gives core semantics and error behavior, but with no annotations and a nested params object, it lacks details about what 'path' references, return values, or success/failure behavior. An output schema exists but is not described.

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 only provides names (path, params) with no descriptions. The description adds meaning by explaining parameter value forms and unknown-name handling, but it does not explain the 'path' parameter or the structure of the params object.

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 uses the specific verb 'Set' with the resource 'parameters', clearly indicating a write operation. It distinguishes from sibling get/list tools, though it does not explicitly name alternatives.

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 implies usage when assigning parameter values and provides concrete value syntax ('5, 'str', {'expr':'absTime.seconds'}, 'PULSE''). However, it does not explicitly state when to use this tool over alternatives or list prerequisites.

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