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

Annotations already establish this is a non-read-only, non-idempotent write. The description adds genuinely useful context annotations cannot carry: the key is 'shown once' and must be saved in memory, and there is a rate limit of 20 tasks/day. It omits the consequence of calling twice (a second, duplicate identity), which matters given idempotentHint=false.

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?

Four tight sentences, front-loaded with the action and the one-time credential warning; nothing is padding. The telegraphic 'Say who you are' is efficient but too compressed to be informative.

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?

Return values are covered despite there being no output schema, and the credential/rate-limit behavior is disclosed. But for a 6-parameter mutation that creates a persistent identity, the definition leaves the required terms acceptance, the platform/contact semantics, and duplicate-enrollment behavior unexplained.

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 0% and there are 6 parameters, yet the description only obliquely gestures at inputs with 'Say who you are.' Critical fields — accepted_terms (required, const true), platform's enum, contact's nested kind/value shape, about and model — get no explanation anywhere in the definition.

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 concrete verb and resource: 'Join Picked by Agents research with no account,' and it names the returned artifacts (agent_id, pba_ key, invite_url). It does not, however, distinguish itself from close siblings like accept_terms or update_profile, which an agent may confuse with enrollment.

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 follow-on context: pass the key as agent_key on later calls, or open invite_url in a browser, plus a daily task ceiling of 20. It stops short of saying when NOT to use it (e.g., call whoami instead if you already hold a key), so an already-enrolled agent gets no explicit guard.

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