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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful disclosure that only metadata/approved fields are returned and that secrets, contacts, and original files are excluded — a data-minimization guarantee the annotations cannot express. It stops short of explaining pagination or what 'authorised' implies for access control.

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?

Two short sentences, front-loaded with the operation, with no repetition. The phrase 'through the existing application' is vague filler that slightly dilutes an otherwise tight definition.

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 no output schema and 0% parameter documentation, the description carries the full explanatory burden. It covers what is excluded from results but leaves the return shape, pagination behavior, and every non-required parameter unexplained — not enough for an agent to invoke this reliably.

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 0%, and the description supplies no parameter meaning at all. It never explains what targetId identifies (a certificate, employee, or location), what query searches over, or that limit/offset are pagination controls, so an agent must infer three of four parameters from their names and constraints.

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 — certificate verification status — with an explicit read verb, which is enough for an agent to know what comes back. It does not differentiate from nearby siblings such as get_certificate_metadata, get_credential_details, or get_credential_workflow_state, so the agent must guess which status view it wants.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. With four similarly named certificate/credential siblings, the description gives the agent nothing to disambiguate the choice beyond the tool name itself.

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