ghl_course_import

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

Annotations indicate readOnlyHint=false (mutates), openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds no behavioral context beyond stating the tool imports courses, failing to disclose what happens on import (e.g., duplicate handling, validation, side effects). Since annotations already provide some info, the bar is lower, but the description contributes little.

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 short and includes the endpoint, which is helpful for debugging. However, it redundantly repeats 'Import Courses' and is somewhat unstructured. Overall, it is mostly 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?

Given the complex nested schema and lack of output schema, the description is insufficient. It does not explain what happens after import, error handling, or response format, leaving the agent without enough context to use the tool effectively.

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 schema fully describes the required 'body' parameter with nested objects. The description adds no additional meaning to parameters, repeating only the tool's purpose. Baseline is 3 due to high schema coverage.

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 clearly states 'Import Courses through public channels' and provides the endpoint. It specifies the verb (Import) and resource (Courses), making the purpose clear. However, the phrase 'public channels' is vague and the description is slightly redundant by repeating 'Import Courses'.

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 is provided on when to use this tool, prerequisites, or how it differs from alternatives. The description gives no context for usage beyond the basic action, leaving the agent without direction on when to invoke it.

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