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

With no annotations, the description carries the full burden and does substantial work: it discloses the email side effect, that no key is minted until the link is opened, that non-allowlisted addresses are rejected, and the partner_id allowlist constraint. It omits auth/permission requirements and rate limits, so not exhaustive, but unusually rich for an unannotated tool.

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 core function ('Primary agentic mint') followed by short, high-density assertions. Every sentence adds a distinct fact (side effect, return value, gating, partner behavior, exclusions) with essentially 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?

For a mint tool with no annotations and no output schema, the description covers the key operational facts an agent needs: the approval flow, the returned poll_token, rejection behavior, and the partner_id branch. It stops short of describing token lifetime, error taxonomy beyond the schema, or auth prerequisites, but the essential call-shaping context is present.

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 coverage is 50% (only partner_id is documented in the schema), so the description must compensate, and it does: it explains the email allowlist/waitlist constraint and that omitting partner_id yields a generic lf_agent_ key versus a partner-claimed one. This adds meaning beyond the schema's UNKNOWN_PARTNER note, though the email param's format is still only lightly characterized.

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 ('Primary agentic mint ... Emails a one-time approve link ... Returns poll_token') with concrete scope. It explicitly carves out what it is not ('Developer keys are not minted here. Founder UI is backup'), letting an agent distinguish it from 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?

Gives clear conditions for use (allowlisted or approved-waitlist addresses) and names the alternatives it is not for (developer keys, founder UI backup). It routes the agent well but never explicitly names the follow-up step (polling with poll_token) or the poll sibling, leaving that to inference.

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