add_customers_to_service_desk

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

No annotations provided. Description only states it 'grants access' without detailing side effects (e.g., idempotency, whether it overwrites, permissions needed). Minimal behavioral disclosure.

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?

Short, structured with bullet points for arguments. Every sentence adds value with no redundancy.

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?

Covers purpose and parameter usage, but omits edge cases like handling both parameters simultaneously, error conditions, or idempotency. Output schema exists, so return values are not needed.

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 coverage is 0%, but the description explains the comma-separated format and environment distinction for usernames/account_ids. Adds meaning beyond the bare 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 clearly states the action ('Grant one or more users access to a service desk as customers') with a specific verb and resource. It distinguishes from sibling tools like remove_customers_from_service_desk.

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 clear guidance on parameter usage: usernames for Server/DC, account_ids for Cloud. Does not explicitly mention when not to use the tool or alternatives, but the context is sufficient.

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