edubase_get_exam_certificates_presets

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description only needs to add context. It adds the useful scope that public, owned, and organization presets are returned, but it does not disclose output details, pagination, or ordering behavior beyond what the schema covers.

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?

Two sentences with no filler; the action is front-loaded and the second sentence adds meaningful scope information. Every sentence earns its place.

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?

With an output schema, read-only annotations, and only two optional parameters, the description is nearly complete. It explains what is listed and the ownership categories returned; a small gap is that it doesn't explicitly connect the optional exam parameter to filtering/ordering, though the schema covers that.

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 schema already documents the exam and language parameters. The description adds no syntax or behavioral details beyond the schema's own parameter descriptions; the baseline of 3 applies.

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 uses a specific verb ('List') and a specific resource ('certificate presets') and narrows scope to presets usable on exams. It also distinguishes this from sibling certificate tools like edubase_get_exam_certificates by describing presets rather than certificates.

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?

The use case is implied: retrieve preset templates that an exam can use, with public/owned/organization sources returned. However, it does not explicitly state when to prefer this over sibling tools such as edubase_get_exam_certificates or edubase_get_exam_certificates_user, nor does it give exclusion conditions.

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