set_custom_property

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

The description only says 'upsert' but does not disclose behavioral traits like whether it overwrites existing properties, size limits, or side effects. No annotations are available to compensate.

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 short and to the point, with a clear list of arguments. However, it could benefit from being structured with more detail without losing conciseness.

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 no output schema details provided, the description lacks information on return values, error conditions, or confirmation of success. It leaves the agent guessing.

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 must compensate. However, parameter descriptions are minimal (e.g., 'Property name') and add little beyond parameter names. The vt_type examples are somewhat helpful but not comprehensive.

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 tool's function: 'Set (upsert) a custom document property.' This distinguishes it from siblings like 'get_custom_properties' and 'delete_custom_property'.

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 provided on when to use this tool versus alternatives (e.g., 'set_properties' or 'set_document_protection'). The description does not mention context or prerequisites.

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