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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, what a 'certificate' contains, whether it is idempotent, what permissions the id requires, or what happens on an unknown id. This is a complete transparency gap for a tool with zero structured support.

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 text is short but not concise in the useful sense — it is under-specified rather than economical, containing a namespace tag and a noun phrase with zero information. There is no front-loaded statement of action to be concise about.

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 tool with no annotations, no output schema, and 0% parameter documentation, the description needed to carry everything and carries nothing. An agent has no basis to decide whether to invoke it or what the required id should be.

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 there is exactly one parameter, 'id', whose meaning is entirely undocumented in both the schema and the description. The description does not say whether id refers to an agent, a trust record, a certificate, or something else, so the caller cannot know what to pass.

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 is essentially a restatement of the tool name plus a bracketed namespace tag. 'Drift certificate' names a resource but supplies no verb and no indication of what the tool actually does with a drift certificate. It is a tautology rather than a stated purpose.

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 guidance whatsoever about when to call this tool, and no mention of nearby siblings such as drift_check, trust_score, trust_decay, or trust_history. An agent cannot infer when this tool is preferred over those alternatives.

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