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

With annotations indicating it is not read-only, not destructive, and idempotent, the description adds context that it changes the model but does not alter existing object values. It does not mention permission requirements or full side effects, but the annotation already covers 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 concise and front-loaded: it states the action, then clarifies its effect, then gives usage guidance, and finally adds a note about not altering object values. Every sentence serves a purpose.

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 tool's complexity (10 parameters) and the presence of detailed annotations and complete schema coverage, the description provides sufficient context to understand its purpose, effect, and usage. It could mention that it requires admin or can_manage_scope permissions, as hinted in the scope_id parameter description, but overall it is adequate.

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 has 100% description coverage, so the baseline is 3. The description does not add any parameter-specific details beyond the schema, which already documents each parameter thoroughly (e.g., scope_id semantics, key requirement).

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 verb and resource: creating a new property set (a group of fields for object types). It also explicitly notes that this changes the model, distinguishing it from tools that modify object values.

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?

It provides clear guidance on when to use this tool: to define recurring field bundles once instead of assigning fields individually. It also clarifies that it does not modify existing object values, implicitly differentiating it from data-modification tools. However, it does not explicitly name alternative tools like onto_property_set_update or onto_property_def_create.

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