Create Property Setter

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Override' is vague—it doesn't explain that this creates a Property Setter record, whether changes are global/persistent, require permissions, or affect existing data. No side effects or prerequisites are mentioned.

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, well-formed sentence with no wasted words. However, it is so terse that it borders on under-specification, providing only the bare definition without helpful context. It is not as egregious as a tautology, but it lacks the substance expected of a genuinely helpful description.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'override' entails, how the required parameters interact, what values are valid, or what the response or side effects are. The schema covers parameter descriptions, but broader context is missing.

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?

The schema provides 100% coverage with descriptions for all four parameters. The description adds minimal semantic value beyond the schema, only noting that 'property' and 'fieldname' relate to DocType-level or field-level targets. This is consistent with the baseline for high schema coverage.

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 'Override a DocType or field property' is a specific verb+resource statement that clearly indicates the tool's function. It distinguishes itself from document manipulation tools like update_document, but doesn't explicitly contrast with related property/customization tools.

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. It doesn't mention scenarios such as needing to change a DocType's custom properties, nor does it exclude cases better handled by create_custom_field or update_document.

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