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

The description discloses the exact runtime behavior (a 501 not_available response) and the backend reason (no certification store), which is far more than a normal read tool would need. This is consistent with readOnlyHint=true/destructiveHint=false and prevents an agent from expecting returned cert records.

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?

Front-loaded with the operative fact ('Answers 501 not_available') followed by the explanation. It is a single dense sentence; the parenthetical is slightly heavy but every clause carries useful information for the caller.

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 zero-parameter stub with no output schema, the description fully accounts for what the caller will get and why, so nothing an agent needs to invoke it correctly is missing.

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 takes zero parameters and the schema is fully empty, so per the rubric the baseline is 4. There is no parameter meaning that the description could add or omit.

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 states exactly what the tool does: it answers a 501 not_available and never returns certification data. That is a specific, non-tautological purpose and it implicitly distinguishes this stub from data-bearing siblings like get_operator_status or get_registration, though it does not name any sibling.

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?

It clarifies that certifications 'typed at registration are the operator's own claim and are not checked', which steers the agent away from treating certs as verified data, but it gives no explicit when-to-use/when-not framing and names no alternative tool for operator provenance.

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