properties-set

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

No annotations are provided, so the description carries full burden. It states the tool 'sets' a property, implying a mutating operation, and mentions JSON-encoding of the value, which is useful. However, it omits critical behavioral details: whether setting is idempotent, whether it can fail on invalid paths, whether it requires pre-existing properties, or any side effects on dependent systems. The description is honest but incomplete.

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, front-loaded sentence that states the action and a key constraint. Zero filler, no redundancy. Perfectly concise.

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 mutation tool with no annotations and minimal schema descriptions, the description should do more. It doesn't explain what a 'stable Properties path' is, how it differs from a non-stable one, what happens when the property doesn't exist, or whether the value must match a specific schema. With no output schema or annotation support, the agent may be left guessing about error handling and return values.

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?

Input schema covers both parameters with titles ('Path to property', 'Value to set'), but descriptions are minimal. The tool description adds only that value is JSON-encoded, which is valuable. The path parameter's semantics ('stable', 'mutable RNA or custom property') are partially described in the schema title but not elaborated. The description does not compensate for the 0% schema description coverage, but the schema itself is self-explanatory for a simple setter.

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 'Set a stable Properties path; value is JSON-encoded' clearly identifies the action (set) and resource (a stable Properties path), with an important qualifier ('stable') that distinguishes it from generic set operations. While it doesn't name sibling tools explicitly, the focus on 'Properties path' makes the target resource unambiguous.

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 explicit guidance on when to use this tool versus alternatives like properties-report or properties-object_report. The phrase 'stable Properties path' hints at a specific use case, but it doesn't explain what 'stable' means or when a user should choose this over other property-related tools. The agent is left to infer usage from the name and description.

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