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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds genuinely new behavioral information: the response is capped at 'at most two focused follow-up questions' and the tool is explicitly framed as not a gate. With no output schema, this return-shape disclosure is valuable; it stops short of saying whether a pass/fail verdict is also returned.

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?

Two short sentences, front-loaded with the core purpose before the clarifying caveat. No filler. The phrase 'not a joining gate' is slightly oblique jargon that costs a re-read, which keeps it from a 5.

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?

It is complete enough to know the call is a safe, read-only readiness check that yields follow-up questions, which is the key framing. But for a tool whose input is a large nested profile graph, nothing is said about what constitutes 'enough' context or what other outputs accompany the questions, leaving the agent to guess the verdict semantics.

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% across two parameters, one of which is a deeply nested profile object with dozens of fields and the other a context object with non-obvious fields like sourceLabels and inferredFields. The phrase 'specific authorized context' gestures at the context parameter but never explains what sourceLabels or inferredFields mean or how they change the assessment. For a schema this complex with zero documented fields, the description does not compensate.

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: checks whether a profile has enough specific authorized context for useful coordination. That is far clearer than the title alone and tells the agent it is a diagnostic/assessment call. It does not, however, distinguish itself from siblings such as find_person_context or preview_profile, so an agent cannot route on name alone.

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 clause 'not a joining gate' implies the assessment is advisory and should not be used to block or reject a profile, which is implicit usage guidance. But there is no explicit statement of when to call this instead of find_person_context or preview_profile, and no prerequisites (e.g. that a profile object must already be assembled) are given.

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