set_custom_property

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

Without annotations, the description carries full burden but only states it sets/upserts. It does not disclose behavioral traits like whether it overwrites existing properties, requires permissions, or has any side effects. The term 'upsert' is present but not explained.

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 very concise with only two sentences, front-loading the main action. The 'Args' format adds structure but not wordiness. Every part contributes, though it could be more streamlined.

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 setter tool, the description is adequate but does not mention return values (especially since output schema exists) or error conditions. The upsert behavior is implied but not clarified. A bit more context on results or failure modes would improve completeness.

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 partially compensates by listing the three parameters and giving a one-line explanation for each. However, 'vt_type' only provides examples ('lpwstr, i4, bool, etc.') without specifying complete allowed values or format, leaving ambiguity.

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 action ('Set (upsert)') and the resource ('custom document property'), distinguishing it from sibling tools like 'delete_custom_property' and 'get_custom_properties'.

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 on when to use this tool versus alternatives, such as when to set vs. update a property or prerequisites like having an open document. The description does not compare to siblings or specify constraints.

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