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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: it discloses the required authorization scope and explicitly rules out side effects (no OAuth, no linking/unlinking, no payment) and any target selection. It stops short of describing the returned payload, but the behavioral surface is well disclosed.

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 short sentences, front-loaded with what is read before the constraints. Every clause earns its place: scope requirement, exclusions, and the pointer to the interactive linking page. No filler or restated title.

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 zero-parameter read tool with full annotation coverage, the description supplies purpose, auth scope, exclusions and the mutation alternative, which is enough to invoke it correctly. The only remaining gap is the shape of the returned identity data, which matters slightly 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?

The tool takes no parameters at all (0 params, additionalProperties false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter documentation gap exists.

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 (read) and resource (the verified key owner's saved ORCID/GitHub identities), with the exact scope qualifier 'verified key owner's' that tells the agent there is no wallet/target selection. It also enumerates what it is not (wallet selector, provider OAuth, linking, unlinking, research, payment), which separates it from linking flows and from sibling read tools like profile_read and research.

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 a clear precondition ('Requires explicit profile:read scope') and redirects the mutating counterpart to the private profile browser page for interactive linking. It does not name a sibling tool as the alternative for reading other profile data, so the routing guidance stops just short of fully explicit.

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