emacs_org_property_set

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

With no annotations provided, the description carries the full disclosure burden for this mutation tool. It conveys only that a property is set, but not whether existing property values are overwritten, whether a property drawer is created if absent, what happens when the heading is not found, or whether the buffer must be saved afterward. An agent cannot anticipate side effects or failure modes.

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 single sentence `Set a property for a heading` is efficiently terse with no filler. However, the brevity borders on under-specification rather than purposeful conciseness — the structural slot that should carry usage and behavior guidance is simply empty.

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 mutating tool with four required parameters, no annotations, and no output schema, this description is incomplete. It omits the behavioral traits an agent needs (overwrite semantics, drawer creation, heading-not-found handling) and provides no routing context among the large sibling set. The schema covers parameters, but behavior and usage remain unpocumented.

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 100%, so the baseline of 3 applies; the schema already documents all four parameters (value, buffer, heading, property). The description adds no parameter-level insight such as property name format, allowed value shapes, or how the heading is matched, but it also has no gaps to compensate for.

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 states a specific verb (`Set`) and resource (`a property for a heading`), which unambiguously names the operation. The term `property` helps distinguish it from siblings like emacs_org_tag_set and emacs_org_todo_set, though it does not explain what an Org property is ( a key-value pair typically stored in a property drawer ), leaving a mild knowledge gap for agents unfamiliar with Org-mode conventions.

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 whatsoever on when to use this tool versus its many org siblings (e.g., emacs_org_heading_update, emacs_org_tag_set, emacs_org_todo_set). The description is a single sentence with no when-to-use context, no exclusions, and no mention of alternatives, so an agent must guess from the name alone.

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