setUserExpiry

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

Annotations already cover read/write and destructiveness. The description adds value by clarifying the reseller scoping and the ability to remove the expiry (via null). It doesn't contradict 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 two concise sentences plus a tag, front-loaded with the primary action. No wasted words; the key business rule is included.

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 simple mutation with one nested object and no output schema, the description covers the main action and a critical constraint. It lacks error/response details, but given the simplicity and annotation coverage, it's 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% parameter coverage, including descriptions for user_id and expiry_date (format and null semantics). The description reinforces the action but doesn't add new parameter-level details, so baseline 3 is appropriate.

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 'Set or remove the expiry date on a child user', using a specific verb and resource. The reseller context distinguishes it from other user-management 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?

The description provides a clear precondition ('must belong to a child organization of your reseller'), which tells the agent when this tool is applicable. It doesn't explicitly mention alternatives, but the scope is well-defined.

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