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

Annotations declare destructiveHint and openWorldHint, but the description adds substantial context beyond them: the confirm:true publishing gate versus preview, that publishing exposes data to anyone with the link, that turning off preserves the link, that hours exclude rates/money, and that the operation is Pro-gated except when disabling an existing portal. This is rich, non-obvious 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?

Front-loaded with the core action and followed by the consequential confirm/publishing rules, so the most important information comes first. It is dense and slightly run-on with parentheticals, but nearly every clause carries load-bearing detail.

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 destructive, open-world mutation with no output schema, the description covers the elements an agent needs: the confirm gate versus preview, the publishing side effect, link persistence, ownership and Pro restrictions, and the first-use creation behavior. Nothing critical for correct invocation is missing.

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 100%, so the schema already documents all nine parameters, and the description largely restates them (welcome text, studio name, sent documents, comments). It adds only marginal flavor, such as noting hours are shown against the budget and that no amounts appear on the portal page. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource with full scope: turns a project's client portal on/off and sets what it displays (tasks, hours, documents, comments, welcome text, studio name). It also clarifies it creates the portal and link on first use, clearly distinguishing it from read-only siblings like get_client_portal and regenerate_client_portal_link.

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 strong conditional guidance: enabling or changing an enabled portal publishes to anyone with the link and requires confirm: true, whereas disabling does not and neither does the preview path. It also states the Pro-feature gating and owner-only restriction. It stops short of naming sibling alternatives explicitly, but the when/when-not conditions are clear.

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