courses_import_courses

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

Annotations already indicate the tool is not read-only (readOnlyHint false) and not destructive (destructiveHint false), but the description adds no behavioral details such as whether it overwrites existing courses, requires external systems (openWorldHint true), or handles bulk operations. The description is redundant with the name and lacks any extra transparency.

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 extremely brief (two words), which is concise but under-specified. It lacks any structure or elaboration that would help an agent understand the operation. While it front-loads the verb, it fails to provide necessary context, making it more of an under-specification than a model of conciseness.

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 tool has three parameters including a required complex array and produces no output schema, the description is woefully incomplete. An agent has no indication of the expected product structure, the purpose of userId, or what the tool returns. This makes the tool effectively unusable without external documentation.

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?

The schema describes only locationId (33% coverage), leaving the required 'products' array and 'userId' undefined. The description offers no explanation for these parameters, their structure, or expected values. With low schema coverage, the description should compensate but does not, making it impossible for an agent to construct valid inputs.

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 'Import Courses' states a clear verb and resource, indicating the action is to import course data. It is concise and unambiguous, though it does not elaborate on the source or format. There are no conflicting sibling tools with a similar name, so it stands out sufficiently.

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?

There is no guidance on when to use this tool, what prerequisites exist, or how it differs from alternatives. The description provides zero context about typical use cases or when not to use it. Without any usage instructions, an agent is left to infer its applicability.

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