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

The description discloses that the tool returns identity info, write permission status, and operator linkage, and notes that the opaque ID is never exposed. However, it does not explicitly state the tool is read-only or what happens on error. Given no annotations, it carries a moderate burden and somewhat succeeds but with confusing language.

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 description is a single convoluted sentence with unnecessary jargon and a confusing dash-separated clause. It is not front-loaded; the key point about returning identity is buried. Could be much shorter and clearer.

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 should fully explain the return structure. It mentions identity, write gate, and operator-linkage but does not specify format, fields, or data types. The cryptic 'confirmation needs no disclosure' adds confusion without clarity.

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?

There are zero parameters, so the input schema covers everything trivially. The description adds context about authentication (Bearer token) and what the tool checks, going beyond the schema. Baseline for no params is 4.

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 starts with 'AUTH:' and mentions returning identity, write gate status, and operator-linkage status, which gives a general sense of the tool's purpose. However, the phrasing is cryptic with jargon like 'agent-first: confirmation needs no disclosure', obscuring the core function. It distinguishes from siblings implicitly by focusing on current user info.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, such as needing a valid token, nor does it contrast with similar tools in the sibling list.

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