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

Goes well beyond the destructiveHint=false/readOnlyHint=false annotations: it discloses that drafts consume no credit and send no e-mail, that publishing consumes a credit and the account silently falls back to unpublished when credits are exhausted, that a Dashboard sandbox setting overrides publish, and that repeat calls create duplicate credentials. These are non-obvious side effects and failure modes that annotations cannot express.

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?

Everything is in one dense but front-loaded paragraph that opens with the WRITE marker, cardinality, and target resource before detailing side effects. Every sentence carries operational weight, though the run-on length makes it slightly harder to scan than an ideally chunked 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?

For a 14-parameter mutation tool with nested objects and no output schema, the description covers the decision-relevant behavior thoroughly (publish semantics, credits, idempotency, scope limits). The main omission is what the call returns, which the agent must infer since no output schema exists.

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%, so the schema already documents all 14 parameters, making 3 the floor. The description still adds meaning the schema lacks: the reliable pattern of supplying your own credential_id to make later lookup possible, and the publish/credit/e-mail consequences of the publish parameter rather than just its type.

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 verb and resource ('creates ONE credential (badge or certificate) for ONE recipient in an existing group') and bounds the cardinality explicitly. An agent can distinguish it from the search_/get_ siblings without opening any schema.

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?

Explicitly routes behavior: default = unpublished draft (no e-mail, no credit), publish=true = immediate publish with e-mail and credit consumption, plus the sandbox-mode override. It also states what this tool does NOT do (evidence, references, bulk issuing, edits, deletes) and warns about non-idempotency, which is precisely the when-to-use/when-not information an agent needs.

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