Get Course Info

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

No annotations are provided, so the description carries full burden. It only states that information is returned, but does not confirm read-only nature, authentication needs, or side effects. The existence of an output schema is not referenced, missing an opportunity to clarify the return structure.

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 a single, concise sentence that is front-loaded with the key purpose. It wastes no words, though it could be slightly expanded to include critical details without losing 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's simplicity (one parameter, no nested objects) and the existence of an output schema, the description could be more complete. It lacks behavioral info and parameter details, but it is adequate for a straightforward read operation. The output schema likely covers return structure, reducing the need for full explanation.

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 single parameter 'course' has no description in the schema (0% coverage), and the tool description adds no explanation about its format (e.g., ID, name, URL). The description should compensate for the schema gap, but it does not.

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 the action ('Return structured information') and the specific source ('Sınıf Bilgileri' page). This distinguishes it from other course tools that target different pages or tasks. However, it lacks details on what structured information is returned, making it less specific than a high score of 5.

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 given on when to use this tool versus alternatives. Given the many similar get_course_* tools, explicit differentiation is needed. The description does not mention prerequisites, context, or when not to use it.

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