ghl_course_sequence_categories

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

Annotations already declare the mutation profile: not read-only, idempotent, non-destructive, open-world. The description adds important auth requirements (Location/sub-account token, courses.write) and the exact endpoint, though it does not explain whether the reorder requires a complete category list or what the response contains.

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 description is front-loaded with the operation and path-parameter clarification, then gives auth and endpoint details. It is mostly efficient, though the version/source metadata is somewhat boilerplate for tool selection.

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 mutation tool with a nested request body and no output schema, the description covers the key operational context: endpoint, authentication scope, and path-parameter meaning. It leaves some minor gaps around return behavior and whether the ordering list must be exhaustive.

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 parameter baseline is 3. The description adds meaning by clarifying that productId is specifically the course/product id and that a Location token is required, going beyond the schema's generic 'Product id' label.

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 states a specific verb and resource: 'Reorder categories in a course.' It also clarifies that the productId path parameter is the course/product id, which removes ambiguity from the tool name.

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?

It gives clear usage context by naming the required Location token and courses.write scope, and the action is distinguishable from sibling category CRUD and lesson-sequencing tools. It does not explicitly say when not to use it or name an alternative tool, which keeps it from a 5.

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