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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful context beyond them: it is a public endpoint (no auth), returns natural-language text rather than structured data, preserves sources and conditions, and handles pagination.

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?

Front-loaded with the core resource and delivered as a single dense sentence that lists the returned fields efficiently. It is a run-on comma-separated enumeration, but no sentence is wasted and nothing is buried mid-paragraph.

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?

With no output schema, the description must describe return values, and it does so thoroughly: round-level records, current pool, announced next round, and a frozen forecast, plus format, sources, conditions and pagination. The main gap is the absence of routing guidance relative to the sibling forecast 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?

Schema description coverage is 100%, covering both occupation (internal code/slug with precedence rules) and locale (enum with default and URL-prefix effect). The description adds no parameter-level detail beyond this, so the schema carries the full burden and 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?

States a specific verb (get) and resource (subclass 189/491 invitation round history for one ANZSCO occupation), then enumerates the exact data returned: round dates, invited status, points cutoffs, pool size, next round date, and forecast. The resource is clear, but it never names the closely related sibling estimate_189_invitation, so the boundary between the historical record and the forecast tool is left implicit.

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 says nothing about when to use this tool versus alternatives, nor any prerequisites. It does not mention estimate_189_invitation or explain whether history and forecast should be fetched together, leaving the agent to infer usage from the content list alone.

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