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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are capped by account tier (1 result for free, up to 50 for VIP) and only 'published' observations are returned. It stops short of describing ordering or what a cutoff observation contains.

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?

Two tight sentences with the resource scope front-loaded and the tier constraint following. No filler or redundancy.

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?

There is no output schema, so the description should carry more of the return-value burden, and it doesn't say what fields a cutoff observation has. Combined with the unexplained query semantics, an agent can call the tool but cannot predict what it will match or receive.

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 the single required 'query' parameter (2-120 chars, no format documented). The description says 'matching observation' but never clarifies whether the query matches an occupation name, ANZSCO code, or free text, leaving the only input underspecified in both schema and description.

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 (search) and resource (published occupation invitation cutoff observations), which an agent can distinguish from siblings like get_invitation_rounds or get_eoi_history. It does not explicitly contrast itself with those closest siblings, so it falls short of a 5.

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 explains the account-tier result limits (free = latest matching observation for one occupation, VIP = up to 50 results), which implies usage context. However, it gives no guidance on when to use this versus get_invitation_rounds, get_latest_overview, or other cutoff-related siblings.

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