q402_wallet_status

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

With no annotations, the description carries the full burden; it explicitly states 'Read-only - no signing, no on-chain TX, no quota consumption' and 'Requires Q402_PRIVATE_KEY in env.' It also reveals the return format per chain. This is strong disclosure beyond the schema.

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?

Three sentences with every clause earning its place: scope, return shape, safety, pairing, and prerequisite. It is front-loaded and compact.

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?

Given a 0-parameter schema and no output schema, the description fully describes the tool's behavior, output structure, and requirements. It also connects to a related sibling, making it contextually complete for selection and invocation.

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 input schema is an empty object, so there are no parameters to document. The description still adds context by identifying the wallet source (EOA derived from Q402_PRIVATE_KEY), which is the implicit parameter, earning a solid 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 opens with the specific verb 'Report' and a precise resource: 'EIP-7702 delegation status of your Q402 wallet across all 12 Q402-supported chains.' This unambiguously distinguishes it from sibling tools such as q402_balance or q402_clear_delegation.

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?

It provides a direct pairing with q402_clear_delegation for resetting a specific chain, and notes the environment prerequisite (Q402_PRIVATE_KEY). However, it does not explicitly state exclusions or alternative tools for other status queries, so it stops short of a full when-to-use/not-to-use guide.

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