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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the behavioral requirement of Authorization: Bearer <JWT>, which is a useful operational detail not in annotations. It also discloses the nature of the response (connections, mandates, actions), providing transparency beyond annotations without contradicting them.

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 two sentences with no fluff. The first sentence front-loads the main content (what is returned) and the second adds the auth requirement. Every part is useful and efficiently conveys the tool's purpose. It is appropriately sized for a zero-parameter status tool.

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 carries the burden of explaining the return value, which it does by listing the types of data (connections, mandates with specific fields, actions with results). It also notes the auth requirement. It does not mention pagination, response format, or any limits, but for a simple status overview, the coverage is sufficient. Minor gaps exist but are not critical.

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 zero parameters, so the baseline is 4 per the rubric. The description adds no parameter-specific semantics because there are none; the schema is empty and there is nothing to explain. The description correctly does not invent parameters, so it meets the baseline.

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 tool's purpose: it returns everything set up in Signet, including signer connections, active mandates with specific details (spend/cap/expiry/session_address), and recent actions with results. This differentiates it from sibling signet tools that perform actions (e.g., signet_action, signet_approve) by emphasizing it's a read-only overview. The resource and scope are explicit.

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 does not explicitly say when to use this tool versus alternatives. It only describes what it returns and mentions the auth requirement. There is no guidance on when to choose it over similar status tools like signet_portfolio or signet_price, nor any exclusions. The usage context is implied but not stated.

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