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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions the core assign/unassign action and the high-level effect, but fails to disclose important behaviors such as the need for confirmation (confirm parameter), set of configurable fields (price, commission), or potential side effects of unassigning (e.g., whether it removes historical data). This is a significant gap for a mutation tool.

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 with the primary action ('Assign or unassign'). It consists of two sentences that each add value: the first specifies the exact operation, and the second clarifies the real-world impact. No wasted words.

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 (8 parameters, no output schema, no annotations), this description is far from complete. It does not explain the optional parameters, the confirmation flow, or expected return behavior. A user would have to guess how price/commission/confirm interact with the assignment, making this inadequate for safe invocation.

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 0%, so the description must compensate by explaining parameters. It only maps 'provider' to providerId and 'service' to serviceId, but does not explain orgSlug, action (beyond assign/unassign), price, commission, confirm, or apiKey. The description adds little meaning beyond what the raw schema already shows.

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 ('Assign or unassign a provider to/from a service') and explains the purpose ('controls which providers can deliver which services'). This distinguishes it from sibling tools like service_update or provider_update, which modify the entities themselves rather than the assignment relationship.

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 implies when to use this tool: to manage provider-service assignments. It provides clear context that this is the tool for controlling provider eligibility for services. However, it does not explicitly mention alternatives or exclusion criteria, such as using admin_set_availability for scheduling-related constraints.

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