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

Annotations already declare write, non-idempotent, open-world behavior, and the description adds meaningful side-effect context beyond them: it 'creates portal access configuration and may provision a hostname and certificate.' The word 'may' usefully signals non-determinism, though permissions requirements and whether certificate provisioning can fail or be retried are left implicit.

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?

Three sentences, front-loaded with purpose, then the usage gate, then the effect. Every sentence carries information and there is no filler; only the effect sentence's 'may provision' could be sharpened.

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 10-parameter mutation with no output schema and no per-parameter schema descriptions, the description adequately frames what the tool does and when to use it but leaves input semantics largely unexplained. An agent could select it correctly but would be guessing on most optional claims fields.

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% across 10 parameters, so the description carries the full explanatory burden. It only gestures at two clusters ('application and identity-provider configuration') and says nothing about hostname, oidcScopes, nameClaim, emailClaim, recipientClaim, or allowedEmailDomain — leaving half the inputs undocumented anywhere.

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 concrete verb and resource ('Configure a customer webhook portal on a domain the user controls, with their existing OpenID Connect identity provider'), which clearly separates it from read-oriented siblings like check_portal_host and list_portal_hosts. It doesn't explicitly name the nearest alternative (save_portal_settings), so sibling differentiation is implied rather than stated.

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?

Gives an explicit activation condition: 'Use only when the user asks to set up a portal domain and supplies the application and identity-provider configuration.' That is a real when-to-use gate backed by required inputs. It stops short of naming when-not or pointing to the settings/list alternatives for partial setups.

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