preview_property_changes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a non-mutating preview but does not explicitly state that no changes are applied, how writability is determined, or what the preview result contains.

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 with no filler or repetition. It is appropriately concise, though it is terse enough that it leaves critical parameter details unexplained.

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?

With no annotations, no output schema, and no parameter descriptions, the tool definition is incomplete for safe or correct invocation. It does not explain the updates array item format, the document_id semantics, or the preview behavior, so an agent would likely need external knowledge.

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%, and the description does not clarify the structure of each object in 'updates' or the role of 'document_id'. 'Writable item fields' gives some context, but not enough to construct valid update objects.

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, 'Preview', and a specific resource, 'direct property edits for writable item fields'. It distinguishes the tool from apply/set siblings by its preview nature, though 'item fields' is somewhat ambiguous and 'preview_changeset' is also a preview sibling.

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?

There is no guidance on when to use this tool versus set_item_properties, preview_changeset, or apply_changeset. No conditions, exclusions, or alternatives are provided; the only usage signal is the verb 'Preview'.

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