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

With no annotations, the description carries the burden of disclosing behavior. It transparently mentions the data source (JSON-RPC), its fallback behavior ('Ankr-backed when RPC_POLYGON is set, public fallback otherwise'), and the exact return data. It does not explicitly state that the operation is read-only or discuss error handling, but the read-only nature is clearly implied and the network dependency is disclosed.

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, dense sentence that front-loads the tool's purpose and immediately provides key details. Every phrase adds value: data source, fallback behavior, and specific return fields. There is no redundancy or fluff.

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 the simplicity of the tool (single parameter, no output schema, no annotations), the description is fully complete. It explains what the tool does, how it works (JSON-RPC with fallback), what it returns (balance, tx count, contract/EOA, risk heuristic), and its place in the tool ecosystem ('base profile'). No critical information is missing for an agent to decide when and how to invoke it.

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?

Schema coverage is 100%, with the single 'address' parameter fully described as a 'Polygon address (0x + 40 hex chars)'. The tool description adds no additional semantic detail about the parameter beyond what the schema already provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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: retrieving a 'Polygon wallet base profile via JSON-RPC'. It specifies the resource (Polygon wallet), the action (lookup/profile retrieval), and the key outputs (MATIC balance, outbound tx count, contract-vs-EOA detection, risk heuristic). This distinguishes it from sibling tools by emphasizing 'base profile' and 'lightweight risk heuristic', differentiating from more specialized tools like pg_wallet_risk_profile.

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 context (a base-level wallet lookup) but does not explicitly state when to use this tool versus alternatives like pg_wallet_risk_profile or pg_wallet_entity_resolve. The phrase 'base profile' and 'lightweight risk heuristic' hints at a quick first-pass check, but no explicit when-to-use or when-not-to-use guidance is provided. This is implied rather than clear direction.

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