academy_certificates

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

No annotations are provided, so the description carries the full burden. It discloses that sign-in is required and that the tool returns public verification URLs, implying a read-only listing behavior. It does not describe exact output shape or edge cases, but for a zero-parameter list tool this is solid 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 one short, front-loaded sentence plus a parenthetical prerequisite. Every word adds value: the verb, the resource, the output detail, and the auth requirement. There is no repetition or filler.

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 (no parameters, no annotations, no output schema), the description is sufficiently complete. It states what is returned (certificates with public verification URLs) and the key prerequisite (sign-in). It could mention empty-result behavior, but that is a minor gap for a simple list tool.

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 tool has zero parameters, and the schema has 100% coverage of that fact. The description correctly does not invent parameter-related details. With no parameters to document, the baseline of 4 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 clear resource ('your earned certificates'), and further specifies the key output detail ('public verification URLs'). This makes its purpose immediately distinct from sibling academy_* tools, which cover lessons, quizzes, playbooks, and other resources.

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 imperative phrasing implies when to use it: when the user needs their earned certificates and verification URLs. The parenthetical '(Requires sign-in.)' adds clear prerequisite context. No explicit alternatives are named, but no certificate-related sibling tool exists, so this is acceptable.

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