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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether the call is read-only, what authentication is required (the access_token parameter hints at a subscriber token but the description never mentions it), what the summary table contains, or how results are returned.

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 only two short fragments, so it is concise. However, the leading 'PRO.' is cryptic and does not front-load useful information, making the structure less effective than it could be.

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?

The tool has a simple one-parameter schema and no output schema, but the description is too sparse to compensate. It does not explain what the summary table includes, whether the endpoint is premium-only, or what an agent should expect to receive, leaving significant gaps for a data-retrieval tool.

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?

There is one optional parameter (access_token) and schema description coverage is 100%, so the schema already documents it fully. The description adds no parameter-level meaning, which meets the baseline 3 for high schema coverage.

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 names a specific resource, the 'Full AEMO NEM summary table', and the word 'Full' implies broader scope than a prices-only sibling like nem_prices. However, the cryptic 'PRO.' prefix is unexplained and there is no explicit verb, so the purpose is clear but not fully polished.

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 nem_all versus siblings such as nem_prices, region, or fuel_search. An agent must infer the choice from the name and description alone, with no stated conditions or exclusions.

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