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

readOnlyHint=true already declares this is a safe read, and the description is consistent with that ('Show'). It adds useful detail about what data is returned (connections, allowance, fees, router credits) but says nothing about authentication requirements for the token parameter, freshness of 'this month', or whether the result covers a billing period partial-to-date.

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?

A single front-loaded sentence that names the verb, the time scope, and the returned fields with no filler. It is efficient, though it could have spent one more clause on the token requirement.

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 two-parameter read-only tool with no output schema, the description covers the data domain adequately, but with 0% schema coverage it leaves a required authentication parameter undocumented. An agent knows what it will get back but not fully what it must supply.

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 description coverage is 0% for two required parameters. The description only implies that 'address' selects whose usage is reported; the required 'token' parameter is completely unexplained, and there is no hint about its format or where it comes from.

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?

States a specific verb and resource: it shows this month's connections, allowance, fees, and router credits for an address, which distinguishes it from siblings like ventru_pricing or ventru_find. The framing is slightly indirect ('connections' rather than 'usage/billing summary'), but the enumerated fields make the purpose unambiguous.

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?

There is no indication of when to use this versus ventru_pricing, ventru_trust_profile, or ventru_inbox, and no prerequisites are given. The agent must infer usage from the field list alone.

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