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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds non-derivable detail: that both fields are overwritten rather than patched, and the rate limit of 30 requests/hour/key, plus the underlying endpoint.

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?

One tightly packed sentence with the write classification and operation front-loaded, followed by overwrite semantics, rate limit, and endpoint. Every clause carries information; nothing is padding.

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 3-parameter write tool with no output schema, the description covers intent, required-value semantics, rate limiting, and the API route. Only the absence of alternative-routing guidance keeps it from being fully complete.

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 coverage is 100%, so the baseline is 3. The description goes beyond it by clarifying that category_name and parent_category_id are full replacements, not optional deltas — resolving the main ambiguity of a PUT-style update.

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 ('rename a category and/or move it to another parent') and fixes the exact scope of the mutation. An agent can distinguish this from classmarker_create_category and classmarker_update_parent_category without opening a schema.

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?

The parenthetical 'send the name and parent_category_id you want it to have' tells the caller exactly what values to supply under overwrite semantics, which is real invocation guidance. It does not, however, name alternatives or state when not to use this tool (e.g., versus update_parent_category).

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