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 clearly states the operation is a search and lists what is returned: 'matching exams with code, certifying body, question count, domain count, and a free practice-exam link.' While it doesn't explicitly declare read-only, the verb 'Search' and the nature of returning results make the behavior transparent. There are no side effects described, which is appropriate for a pure lookup.

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 three sentences long, front-loaded with the primary action, followed by illustrative examples and a concise enumeration of the return fields. There is no redundant wording; every sentence earns its place, and the structure lets an agent quickly grasp what the tool does and when to use it.

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 four parameters, no output schema, and no annotations, the description provides sufficient context: the search scope, supported query formats, trigger scenarios, and return types. It does not mention pagination or default limit, but these are already encoded in the input schema (limit with min/max and default). The description is complete enough for an agent to call the tool correctly without additional knowledge.

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%, and each parameter has a clear description (e.g., 'Keywords: certification name, exam code, vendor, or topic'). The description adds examples of query values but does not introduce new meaning beyond the schema. As a result, it meets the baseline of 3, relying on the schema to clarify parameter semantics.

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 opens with a specific verb ('Search') and a precise resource ('current Cert Atlas certification and professional exam index'), and enumerates the search keys (name, code, certifying body, vendor) plus concrete examples (AWS Solutions Architect, CISSP, PMP). This clearly differentiates it from sibling tools like compare_exams or get_exam_blueprint, which are not search operations.

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 an explicit trigger: 'Call this whenever a user mentions a certification or exam — e.g. ... — or asks what certs a body offers.' This is strong guidance for when to invoke the tool. However, it does not mention alternatives or exclusions (e.g., when to use compare_exams instead), so it's not fully discriminative.

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