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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is fully covered. The description adds nothing behavioral beyond a field list: it doesn't say what 'documented' means, whether results are paginated, how results are ordered, or whether an empty result is normal — all relevant to a multi-result query tool.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined editing.

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?

An output schema exists, so explaining return fields is redundant, and that is nearly all the description does. With three undocumented parameters, no usage guidance, and an optional-filter surface, the definition leaves an agent without what it needs to pick filters or decide when this tool is the right one.

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?

All three parameters (limit, query, includeSkills) have 0% schema description coverage, so the description must compensate and does not. 'Skills focus' only faintly hints at includeSkills, and query semantics (what fields are searched, the minLength 2 requirement) and the limit default/cap are never addressed.

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?

States a specific resource (certificates) and enumerates the fields returned (issuer, credential ID, verification URL, skills focus), which distinguishes it from get_career_education and get_career_timeline. It never explicitly says how it differs from those siblings, though the resource noun does most of the work.

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 no indication of when to call this versus get_career_education, get_career_timeline, or get_professional_profile. There are no prerequisites, no exclusions, and no mention of the filter/pagination options an agent would need to choose it deliberately.

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