update_org_custom_property_default

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

The description adds behavioral context about propagation, but does not disclose side effects (e.g., whether existing child property values are overwritten), permission requirements, or the nature of the update (e.g., synchronous vs. async). Annotations only indicate it is not read-only and not destructive.

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: two sentences that first state the core purpose and optional propagation, then clarify the role of propagationType. No unnecessary words or repetition.

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?

Given the complexity (8 parameters, no output schema), the description covers the basic operation but lacks details on return value, error scenarios, or what happens to existing default values in child org units. The agent might need more context to handle responses.

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 coverage is 100% with detailed parameter descriptions. The description adds value by explaining that propagationType controls which hierarchy levels receive the update, tying the parameter to the overall operation. This supplements the schema's enum descriptions.

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 (update) and the specific resource (default value of an org-unit custom property), and distinguishes from sibling tools like 'update_org_unit_custom_property' and 'get_org_custom_property_default' by mentioning propagation.

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?

The description implies usage for updating default values with optional propagation, but lacks explicit guidance on when to use this tool versus alternatives like 'update_org_unit_custom_property' or when not to use it (e.g., for read-only queries).

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