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

Annotations already declare a non-readonly, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description's definition of a portal usefully implies that menus, dashboards and access rights are configured afterwards by other tools, but it says nothing about naming collisions, what default state the portal lands in, or visibility/publication.

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 sentences, front-loaded with the action, and the second sentence earns its place by defining the resource. No filler.

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?

With 5 fully documented parameters, no output schema and complete annotations, the description covers enough to invoke the tool correctly. It could go further by noting the typical follow-on setup steps, but nothing required for a correct call 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%, and color/theme/default_permissions carry unusually detailed semantics (enumerated values, the theme:2 exclusion), so the schema does the heavy lifting. The description adds no parameter-level meaning at all, which is the expected baseline for a fully documented 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?

States a specific verb and resource ("Create a new portal") scoped to a project, and adds a useful definition of what a portal is (menu, dashboard, access rights). It doesn't explicitly contrast with adjacent sibling creators like create_portal_page or create_portal_group, so an agent must infer that this tool creates the container, not its parts.

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 guidance on when to create a portal versus the many adjacent tools (create_portal_group, create_portal_page, add_portal_menu_item, invite_portal_user). No prerequisites beyond the implied project context, no note that app_id must come from list_projects (only the schema says that).

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