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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered by structured data. The description adds the subscription requirement, which annotations cannot express, but says nothing about result limits, pagination, or how matches are ranked across the three entity types.

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 short sentences with the scope stated first and the access prerequisite second; nothing is redundant or padded.

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 carries the burden of telling the agent what comes back — presumably matching training organisations, qualifications and units — but it never describes the response shape or whether results span all three entity types in one list. It is adequate to call the tool but leaves the result interpretation underspecified.

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?

Only one parameter exists and schema description coverage is 100% ('a name, code or keyword'), so the schema already carries the meaning. The description adds no syntax, matching-behavior, or format detail (e.g. how an RTO code is matched versus a keyword) beyond what the schema states.

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 a clearly scoped resource: Australia's national register of training organisations, qualifications and units. That scope implicitly separates it from rto_profile (single profile) and list_topics, but the description never names those siblings or states the contrast explicitly.

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 prerequisite 'Requires an RTOpacks subscription' is useful and is the kind of gate an agent needs to know before calling. However, there is no explicit when-to-use vs when-to-use-rto_profile guidance and no statement of what to do if the subscription is missing, so usage is only implied by the resource scope.

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