validate_property

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds the behavioral guarantee 'without saving', which aligns with the read-only intent. It also clarifies that validation is against 'declared type constraints', providing context about what is checked. It does not describe failure responses, but the annotations cover the safety profile.

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 that omits all redundant words. 'Validate a property value against its declared type constraints without saving' conveys purpose, scope, and side-effect behavior efficiently.

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?

The tool has a simple operation with two parameters and no output schema, and the description adequately covers what it does and its non-mutating nature. It does not explain return values, but this is acceptable for a validation tool where the success/failure result is intuitive.

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 100% for both parameters, so the schema already documents that 'name' is a property name and 'value' is a value to validate. The description adds 'declared type constraints' which gives context that validation uses the property's type, but does not add per-parameter details beyond the schema.

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 uses the specific verb 'Validate' and identifies the resource as 'property value', with the scope 'against its declared type constraints without saving'. This clearly distinguishes it from sibling tools like validate_artifact, validate_query, and validate_deployment.

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 phrase 'without saving' clearly implies the tool is intended for pre-save validation, distinguishing it from property-setting tools like set_system_property or bulk_set_properties. However, it does not explicitly name alternative tools or state when not to use it.

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