N1Mm Performance

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

With no annotations, the description carries the full burden, and it does disclose return content plus a useful interpretive note ('rate derivative for band exhaustion detection'). However, it never states that this is a read-only operation, whether the band/mode filters narrow only the rate/breakdown sections or the whole snapshot, or any cost/latency characteristics.

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 headline sentence front-loads the scope, and the second paragraph enumerates contents efficiently. There is mild redundancy ('score' and 'bands' appear in both sentences), but overall it is tight and well-ordered.

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?

An output schema exists, so the detailed return-value enumeration is largely duplicative; the description's marginal value is the snapshot framing and the band-exhaustion hint. What is missing is the decision context — when an agent should prefer this consolidated view over n1mm_current_state or n1mm_contacts.

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 100%, so the schema already documents band, mode, and station_name. The description adds nothing about parameter behavior, including the important question of how filtering interacts with the reported aggregates; baseline 3 applies.

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 the resource clearly ('complete performance snapshot') and enumerates the dimensions it covers (score, rate, bands, run/S&P, timeline), so an agent knows what it retrieves. It does not, however, differentiate itself from siblings like n1mm_current_state or n1mm_multipliers, which could plausibly overlap.

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 when-to-use guidance, no statement of prerequisites, and no reference to an alternative tool. The intended context ('use this when you want a consolidated performance view rather than individual stat tools') is left entirely to inference.

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