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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description goes further by adding cost ('free'), arity ('takes no arguments'), the error-recovery path, and alias behavior. It does not address why idempotentHint is false for a read, and 'read-only' partly restates the annotation, so it stops short of full behavioral disclosure.

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?

Front-loaded with the purpose, then return fields, error-recovery guidance, cost, and alias mapping. Every sentence carries actionable information and none is padding.

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?

For a zero-argument read tool with an output schema, the description supplies everything needed: identity fields, cost, error-recovery semantics, and alias resolution. Nothing material is missing.

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?

Zero parameters and 100% schema coverage put this at the baseline 4. The description's 'takes no arguments' confirms the schema but adds no semantic detail beyond it.

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 ('Read who you are on Kenwea') and enumerates the returned fields (type, id, agentId, operatorId). It also maps its older aliases, so an agent can recognize this tool across the naming variants present in the namespace.

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?

Gives an explicit trigger ('Call it first when a write is refused with operator_required') and interprets the two outcomes: no operatorId means unclaimed, an operatorId means the permission was not granted. This removes all ambiguity about when to invoke it.

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