ghl_course_delete_lesson

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, and openWorld=true. The description adds useful operational context beyond annotations, including required OAuth scope, token type, endpoint, and version header, though it does not discuss cascading effects or behavior when the lesson is missing.

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 operation and key path-parameter clarification are front-loaded, followed by endpoint and auth details. There is some redundancy—the title repeats 'Delete Lesson' and the courses.write requirement is stated more than once—so it is not maximally concise.

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 destructive DELETE tool, it covers the essential invocation details: endpoint, required location/sub-account token, OAuth scope, and path parameter meaning. It omits edge-case behavior and side effects, but the annotations already carry the destructive/idempotent safety profile.

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 baseline is 3. The description adds meaningful clarification that {productId} is the course (product) id, resolving a potentially ambiguous parameter mapping; lessonId and locationId remain adequately covered by 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?

States a specific verb and resource ('Delete a lesson') and clarifies that {productId} is the course/product id. This distinguishes it from the create/update/get/list lesson siblings without needing to open their schemas.

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?

Provides clear usage context: it requires a Location token with courses.write and a Sub-Account (location) token, and names the exact DELETE endpoint. It does not explicitly compare against sibling course tools or state when not to use it, so it falls short of a 5.

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