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

Annotations already declare the mutation/access profile (readOnly=false, idempotent=false, destructive=false). The description adds genuinely useful context beyond them: the link is 'temporary', it 'grants access to that customer's webhook controls', and it carries a security warning. It stops short of explaining expiry defaults or that each call mints a fresh link.

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?

Two tight sentences: purpose first, security caution second. Nothing is redundant and the critical constraint is front-loaded.

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 7-parameter, nested-object mutation tool with no output schema and 0% schema coverage, the description explains only the high-level intent. It omits what the call returns (URL/expiry), how long the session lasts by default, and most parameter meaning, so an agent lacks enough to invoke it confidently.

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 carry the param burden, yet it only maps to the two required fields (appId, recipient). The other five parameters (theme, returnUrl, capabilities, recipientName, expiresInSeconds) get no mention, leaving a large gap.

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') and resource ('temporary customer webhook portal link') scoped to an app and recipient. It is clearly distinguishable from siblings like create_portal_host and check_portal_host, though it never names those alternatives explicitly.

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?

No guidance on when to use this versus related portal tools (create_portal_host, check_portal_host, get_portal_settings). The only usage note is the security caution 'share only with the intended user', which is context, not when-to-use routing.

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