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

No annotations are provided, so the description carries the burden. It discloses that the tool checks credential issuance and returns credential details if verified, which is useful. However, it does not describe what happens when the hash is not verified (e.g., error vs. empty result), whether any side effects occur, or any rate limits. For a read-only verification tool, this is adequate but not rich.

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 compact and front-loaded with the core purpose in the first sentence. The Args section is minimal and useful. It earns its place without fluff, though the second sentence ('Checks if a VerifiedSkillCredential has been issued') is slightly redundant with the first.

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?

The tool has one parameter, no annotations, and an output schema exists. The description covers the input and the basic behavior, but it doesn't describe the output structure or what 'credential details' means. Since an output schema exists, the return format is presumably structured, but the description could still clarify the verification outcome semantics (e.g., what a non-verified hash returns). Adequate for a simple tool but with gaps.

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%, so the description must compensate. It does explain the skill_hash parameter with an example format ('sha256:a1b2c3...'), which adds value beyond the schema's bare string type. However, it doesn't specify the exact format requirements (e.g., length, allowed characters) or whether the 'sha256:' prefix is mandatory. The single parameter is reasonably documented but could be more precise.

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 clearly states the tool verifies an AI agent skill by its canonical SHA-256 hash and checks whether a VerifiedSkillCredential has been issued. It distinguishes itself from sibling tools like mt_skill_issue_vc and mt_skill_audit by focusing on verification, though it doesn't explicitly name those alternatives.

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 implies usage: call this when you have a skill hash and need to check if a credential was issued. It does not explicitly state when to use this over siblings like mt_skill_audit or moltproof_verify, nor does it mention any prerequisites or exclusions. The context is clear enough for a simple verification tool but lacks explicit routing guidance.

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