properties-unset

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

There are no annotations, so the description must carry the burden. It discloses the operation's effect (unset/reset) and restricts scope to resettable RNA properties, but it does not state consequences for invalid/missing paths, reversibility, or any permission 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 a single front-loaded sentence that conveys action, resource, and method without filler. Every word adds meaning.

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 one-parameter tool with no output schema or annotations, the description gives the core operation and path semantics. It is minimally complete, but it omits failure behavior, expected return/confirmation, and how to discover valid stable paths.

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?

With 0% schema description coverage, the description compensates partially by explaining that the path is a stable Properties path identifying a custom/resettable property. However, it provides no syntax, examples, or details on how to format the path beyond the schema title.

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 a specific verb ('Unset') with a clear resource ('custom property or resettable RNA property') and the mechanism ('stable Properties path'). This distinguishes it from sibling tools like properties-set, properties-get, and properties-report.

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 given for when to choose this tool over properties-set or properties-get, and there is no explicit context for resettable vs custom properties. The purpose is implied by the verb but alternative usage is not addressed.

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