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

Annotations only say non-readonly/non-idempotent; the description adds the material facts an agent can't infer: the key's restricted permission set, the one-time-only secret return, the required scope, and the leakage risk. That is exactly the behavior context a minting mutation needs.

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?

Three sentences, each doing distinct work: identity/scope, capability boundary, secret-handling rule plus auth scope. Front-loaded with what is created, no filler.

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, the description carries return semantics itself and does so ("the secret is returned once"). Auth scope and safety handling are covered; the only real gap is the unexplained label parameter, so it is near-complete for a 2-parameter creation tool.

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 carry parameter meaning, and it only half does: "for one project" implies project_id's role, but the "label" parameter (max 100 chars) is never mentioned or explained. An agent gets no guidance on what label is for or whether it must be unique/meaningful.

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?

Specific verb ("Mint") plus resource ("restricted server key") with the key prefix, scope (one project), and audience (server-side environment). The capability list (create sessions, mint connection tokens, read manifests) further pins down exactly what the minted artifact is, distinguishing it from sibling creators like create_connection_token or create_session.

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 states the intended context ("for the app's server-side environment") and the prerequisite ("Requires scope keys:mint"), and gives explicit do/don't handling instructions. It stops short of naming an alternative tool or an explicit when-not-to-use-this case (e.g., when a client-side key would be needed instead).

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