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

Annotations declare destructiveHint=true and idempotentHint=true, which tells the agent this can overwrite/tear down existing portal state, but the description says nothing about what gets destroyed, whether an existing portal config is replaced, or auth needs. With a destructive mutation and rich annotations, the description should disclose the destructive consequence and instead stays silent.

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?

A single tight sentence with no filler, front-loading the action and the resource. It is appropriately sized but arguably too sparse given the destructive nature of the operation.

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, idempotent mutation with a nested config object and no output schema, the description omits what enabling actually does, how config merges interact with existing portal settings, and what happens on repeat calls. An agent lacks the context needed to invoke this safely.

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% and the schema already documents id, type, config (merged in), and status, including the default. The description's 'sales banner, client review, demo' merely restates the type examples already in the schema, so this is the baseline 3.

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 (enable) and resource (portal UI) tied to the published site, plus the concrete variants (sales banner, client review, demo). It does not differentiate itself from the sibling get_portal or remove_portal, so the agent can't be fully certain of the boundary from the description alone.

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 statement of when to choose this tool over get_portal (read) or remove_portal (tear down), and no prerequisites or preconditions such as requiring a published site. Usage is only loosely implied by the listed portal types.

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