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

With no annotations, the description carries the full burden. It discloses that the tool requires an 'authenticated' agent, which is a key behavioral trait. However, it does not mention error conditions, side effects, or whether it is read-only (though 'return' implies so). It lacks details beyond the basic return value.

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, front-loaded sentence with no unnecessary words. The '[Sell]' prefix is cryptic and unexplained, slightly detracting from clarity, but the core description is concise and to the point.

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 simple tool with no parameters, no output schema, and no annotations, the description gives a high-level overview of the return value ('identity and wallet balance'). However, it does not specify the response format or structure, nor does it describe behavior under error conditions (e.g., unauthenticated requests). This is a minor gap for such a simple tool.

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 has 0 parameters, so the schema is vacuous. According to the rubric, a baseline of 4 is appropriate because there are no parameters to document. The description does not need to add parameter semantics.

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 clearly states the verb ('Return') and the resource ('authenticated agent identity and wallet balance'), making the tool's function unambiguous. It also distinguishes itself from the sibling 'wallet' tool by combining identity with balance, and the parenthetical '(publisher identity check)' adds context.

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 via the phrase 'publisher identity check,' suggesting when it might be needed. However, it does not explicitly mention when to use this tool over alternatives (e.g., 'wallet' for balance only), nor does it state any exclusions or prerequisites beyond being authenticated.

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