get_certifications

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description adds that credentials are verified and includes badge verification URLs and IDs, which is useful context. However, it does not mention any limitations such as pagination or data freshness.

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 sentence, front-loaded with the key action ('Retrieve verified 5x multi-cloud credentials') and includes specifics. It is concise and free of fluff.

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, parameterless tool with annotations covering safety, the description is sufficiently complete. It specifies the content (credentials, URLs, IDs) and scope (multi-cloud). There is no output schema, but the description provides a clear sense of what to expect.

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?

With zero parameters, the schema provides no parameter information. The description clarifies what the tool returns (verification URLs, IDs) but doesn't need to explain parameters. Since there are no parameters, the description adequately compensates.

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 tool retrieves verified multi-cloud credentials, including badge verification URLs and credential IDs, specifying the cloud providers (AWS, Azure, GCP, OCI). It distinguishes from siblings like get_skills or get_projects by focusing on certifications specifically, though it doesn't explicitly differentiate from potential certification-related siblings.

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 implies the tool is used when certification data is needed, but does not explicitly state when to use it over alternatives. Sibling names like get_skills and get_profile suggest related but different purposes, yet no explicit guidance is provided.

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