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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: it discloses that the response is role-dependent, with budget books, open operations, and running jobs visible only to the operator. That auth-scoped output variation is the kind of thing annotations cannot express.

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?

It is a single sentence with the resource front-loaded and no filler, which is good. But the bulk of it is a semicolon-delimited enumeration of returned fields that the output schema already documents, so a large share of the text does not earn its place as guidance.

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?

Because an output schema exists, the description does not need to enumerate return values, and the role-conditional note is a valuable addition. What is missing is anything about when this snapshot should be taken versus the many sibling inspection tools, which is the main decision an agent faces here.

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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Nothing in the description misrepresents or omits parameter behavior.

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 names the resource ('the node's own cell') and enumerates the facets it reports (account and roles, anchor state, binding verdict, skills, policy summary), so the general purpose is inferable as a status snapshot. However, there is no verb and no differentiation from adjacent status/inspection siblings such as identity_resolve, kya_check, safety_status, or docs_status, so an agent cannot tell from the text alone why it would pick this one over those.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, despite a sibling set containing at least four overlapping inspection tools. The only conditional statement ('for the operator also...') describes output variation by role, not when to invoke the tool.

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