get_assignment_completion_certificate

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

With no annotations, the description carries the behavioral burden. It discloses that this is a GET request, implying a read-only, non-destructive operation, and it reveals the endpoint structure. However, it does not mention authentication requirements, error behavior, or what happens when the certificate does not exist.

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 only two sentences, front-loads the core purpose, and includes the endpoint plus parameter placement without unnecessary filler. Every sentence contributes value.

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 simple GET tool with an output schema, the description provides the endpoint and the general split between path and query parameters. It is incomplete because it omits the exact route parameter name and does not clarify whether body should ever be used, creating potential confusion for an agent.

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 provides zero property descriptions, so the description's guidance that route IDs belong in path_params and filtering/pagination/sorting/include values belong in query adds useful meaning. It does not, however, specify the exact path key such as assignmentId or explain how body is used, leaving meaningful ambiguity.

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 states a specific action ('Get') and a specific resource ('a learner's assignment completion certificate'), and it names the exact endpoint. It is clear and unlikely to be confused with siblings, though it does not explicitly differentiate itself from similar assignment-related getters.

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 description gives mechanical guidance about putting route IDs in path_params and query values in query, but it does not explain when to use this tool versus alternatives such as get_assignment or get_assignment_learner_activity. No context about prerequisites, typical use cases, or exclusions is provided.

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