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

Annotations already declare readOnlyHint=false, destructiveHint=true, non-idempotent and non-open-world, and the description adds nothing beyond them (no auth requirements, no side effects, no scope). It does not contradict the annotations, but it contributes no behavioral context of its own.

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 two sentences are redundant restatements of the same idea, which is waste rather than conciseness. Nothing is front-loaded with useful information because no useful information is present.

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 tool with nine parameters, a nested config object, no required fields, and no output schema, the description is completely inadequate. An agent learns nothing about what a valid portal creation requires or what happens on call.

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 (name, slug, color, config, etc.), giving a baseline of 3. The description adds no parameter meaning whatsoever, so it neither helps nor hurts beyond the schema.

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 merely restates the tool name and title: 'Add a new portal. Add a new portal to account.' It states a verb (add) and resource (portal) but offers no differentiation from siblings like update_portal, delete_portal, or list_portals, and 'to account' adds no useful scope information.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The second sentence is a near-verbatim duplicate of the first rather than a situational hint, so an agent gets no routing information.

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