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

With no annotations, the description carries the full behavioral burden, but it discloses very little. It does not explain what 'PRO' means, whether an access token is required and how to obtain it, what the summary row contains, or any rate or permission constraints.

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 short sentence, which is efficient, but the unexplained 'PRO.' fragment and the overall terseness make it under-specified rather than genuinely concise. The useful region examples are front-loaded.

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 tool with no annotations and no output schema, the description should clarify authentication, return content, and how it relates to sibling tools like nem_prices and nem_all. It does not, leaving significant gaps an agent would need to resolve before calling it confidently.

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 50%. The access_token parameter is documented by the schema, while the region parameter is undocumented there but partially compensated for by the description's list of region IDs. The description adds some meaning for region but does not explain the access_token parameter or the required format beyond the schema's own text.

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 identifies the resource as a 'NEM summary row' scoped to a region id and gives concrete region values, which is useful. However, it lacks a clear action verb and the cryptic 'PRO.' fragment leaves the operation partly ambiguous. It hints at being different from nem_all and nem_prices but does not explicitly distinguish itself from those siblings.

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 guidance on when to use this tool versus nem_all, nem_prices, or the fuel-related siblings. The region examples are parameter values, not usage conditions. No prerequisites or exclusions are provided.

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