sd_set_node_parameter

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

Annotations indicate idempotent, non-destructive, and non-read-only. The description adds that the tool reads and validates the runtime SD type before setting, which is useful context beyond annotations. However, it does not disclose potential side effects or behavior on type mismatch.

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 a single sentence of 14 words, front-loaded with the action, and contains no redundant information. Every word earns its place.

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 tool's complexity (nested NodeRef, validation step) and the presence of an output schema (which reduces need to explain return values), the description lacks essential context: how to construct the NodeRef, what property_id represents, and the implications of the validation step. It is incomplete for an agent unfamiliar with the domain.

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%, so the description must compensate. It only hints that the value must be a supported simple parameter validated against runtime type, but provides no details on the NodeRef structure or property_id meaning. This is insufficient for a 3-parameter tool with a nested 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 clearly states the tool sets a parameter on a node, using specific verb 'set' and resource 'parameter'. However, it does not differentiate from sibling tools like sd_list_node_properties or sd_create_node, and the term 'supported simple parameter' is somewhat vague.

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. The description implies a prerequisite (validating the runtime SD type), but does not explicitly state when or when not to use it, nor mention any sibling tools.

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