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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description builds on that by noting idempotency ('safe to repeat'), that it 'reads current server state and does not manufacture company facts', and the pendingInvites offer behavior. The generic confirmation-boundary boilerplate prevents a 5, but there is no contradiction with the annotations.

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 first sentence is concise and front-loaded, but the rest is bloated with boilerplate: 'Canonicality', 'Idempotency', and especially the 'Confirmation boundary' sentence list categories like 'reversible save' and 'link preparation' that are irrelevant to an identity read. 'plus every prerequisite stated above' is tautological, so several sentences do not earn their place.

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?

This is a low-complexity tool with no required parameters, read-only annotations, and no output schema. The description covers the core return value (user + org), the pendingInvites conditional, and the prerequisite, so an agent can call it correctly. It would be a 5 if it specified the exact response shape, but that is a minor gap for an identity lookup.

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 100%, and the only parameter (_corply_context) is already described in the schema as echoing context_engineering.context_session. The description adds no parameter-level meaning, so the schema carries the burden and the baseline of 3 applies.

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: 'Return the resolved caller identity (user + org)' and adds conditional behavior around pendingInvites. It is clear, but it does not explicitly distinguish itself from sibling tools like get_org or get_status, leaving some differentiation to inference.

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?

The description implies usage by defining the operation and gives explicit downstream guidance ('If pendingInvites is non-empty... offer to join') plus an authentication prerequisite. However, it does not say when to prefer this tool over alternatives such as get_org or get_status, and 'plus every prerequisite stated above' is circular rather than informative.

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