netintel_wallet_status

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

With no annotations, the description carries the full burden and does well: it discloses that the call is free and local ('no NetIntel call'), and it enumerates the returned state including spend limits and how much this session has authorized. It stops short of stating permissions/auth requirements or explicitly confirming the operation is read-only and side-effect free, which is a minor residual gap.

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?

Two sentences, both load-bearing: the first enumerates the inspected state, the second fronts cost/locality and then the usage triggers. No filler, and the scope statement leads before the usage conditions.

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 and no annotations, the description compensates by spelling out the return fields (key state, address, USDC balance on Base, per-call and per-session limits) and the situations that should prompt the call. Nothing needed to invoke it correctly 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?

The tool takes zero parameters, so the baseline is 4. There are no inputs to document, and the description correctly spends its words on return content instead of inventing parameter guidance.

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?

Names a specific verb ('Check') and a specific resource ('the agent wallet this MCP server pays NetIntel with'), then enumerates exactly what is returned: key-configured state, address, USDC balance on Base, and per-call/per-session spend limits. This is clearly distinct from the sibling wallet tools (netintel_wallet_balance, netintel_wallet_intel), which operate on arbitrary wallets rather than the agent's own payment wallet.

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 explicit trigger conditions: 'Use when a paid tool reports Payment required or SPEND_LIMIT, before funding, or to confirm a top-up arrived.' This tells the agent both when to call it and what upstream signal should route it here, with no inference required.

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