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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=false. The description adds only that the category attaches to a portal, and omits any note on non-idempotency (repeat calls create duplicates) or the destructive flag's odd fit for a create operation.

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 second sentence is a near-verbatim duplicate of the first and earns no place. Two sentences deliver a single idea, so the text is redundant rather than efficiently 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 an 8-parameter, non-idempotent mutation tool with no output schema, the description supplies no information about the required portal_id, the effect on the portal's category ordering, or what the call returns. Annotations cover the safety profile, but the description leaves the operational picture largely unfilled.

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 eight parameters are fully documented in the schema and the baseline is 3. The phrase 'to portal' loosely ties to the required portal_id, but the description adds no syntax, format, or default information 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 restates the tool name and title ('Add a new category. Add a new category to portal.') without stating anything the structured fields don't already say. It does name a verb and resource, but offers zero differentiation from siblings like update_category, delete_category, or list_categories.

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 update_category (existing category) or delete_category, and no prerequisites such as needing an existing portal. The only contextual hint is 'to portal,' which implies portal scoping but stops far short of when/when-not guidance.

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