create_user_criteria

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

Annotations already indicate a write operation (readOnlyHint false) with potential side effects (openWorldHint true). The description adds the WRITE_ENABLED=true requirement, which is useful context. However, it does not disclose what happens on creation (e.g., whether it overwrites, duplicates, or affects existing records) or how it handles the nested 'fields' object. It adds minimal behavioral detail beyond annotations.

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 sentence, concise and front-loaded with the action and purpose. It states the requirement at the end without unnecessary words. Every word earns its place, making it highly efficient for an agent to parse.

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 has 6 parameters, including a nested object, and no output schema, the description is too sparse. It doesn't explain the relationship between parameters (e.g., how match_all affects behavior), doesn't mention that name is the only required field (though schema states it), and doesn't describe the return value or error handling. An agent would need to infer much of the behavior from parameter names and the table context, which is risky for a write operation.

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 provides descriptions for all 6 parameters (100% coverage), so the description adds no new parameter-specific meaning. It doesn't explain how roles, users, groups, and match_all interact, nor does it clarify the purpose of the nested 'fields' object. Since schema coverage is high, a baseline of 3 is appropriate, but the description does not enhance understanding 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?

States a specific verb 'Create', a specific resource 'user criteria record', and a purpose 'for catalog entitlement/audience'. It clearly identifies the table 'user_criteria' and distinguishes from generic create_record and assign_user_criteria, which would assign existing criteria. The description leaves no ambiguity about what the tool does.

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?

Provides no guidance on when to use this tool vs. alternatives. The only hint is the prerequisite 'Requires WRITE_ENABLED=true', but it doesn't name sibling tools like assign_user_criteria or generic create_record. There is no mention of when to prefer this over other create operations, so an agent must infer usage from the name alone.

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