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

Beyond the readOnlyHint=true annotation, it discloses meaningful behavior: DOB is shown only to this person and must never be repeated afterward, and the returned disclosure must be shown verbatim and is not a signature. The idempotency and confirmation-boundary sentences add a little more, though they read as formulaic boilerplate rather than tool-specific insight.

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?

The core purpose and the DOB/disclosure rules are front-loaded and valuable, but the trailing 'Canonicality / Idempotency / Confirmation boundary' block is long, template-like, and not specific enough to earn its space.

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 usefully previews what is returned (prefilled identity details including DOB and the verbatim disclosure text) and covers safety and prerequisites. The main gap is the unexplained joinCode, which an agent needs in order to call the tool with a correct value.

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% and neither of the two parameters is documented. The description hints that the target is an invitation addressed to the caller's verified email, which loosely implies what joinCode identifies, but it never explains joinCode's format or role, and the nested _corply_context object is entirely unaddressed.

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?

The description states a specific verb and resource: it reads the caller's own personal identity plus any incorporator-supplied draft for an invitation tied to their verified email. This is clearly separable from siblings such as approve_invited_identity or redeem_invite, which act on the invitation rather than merely reading it.

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 gives clear usage context (so the person can verify or correct details instead of retyping) and an explicit prerequisite (authenticated active company access). It implies a before-approval workflow but never names the approving sibling (approve_invited_identity) as the alternative that follows.

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