search_datasets

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

No annotations provided, so description carries full burden. It describes the fuzzy search behavior, result ranking, and curation. Does not explicitly state read-only nature, but the term 'search' implies no side effects. Provides return format details.

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?

Description is well-structured with a brief intro, usage guidance, and examples. It is front-loaded and each sentence adds value. Examples are helpful but slightly verbose, though this is acceptable for clarity.

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?

Given the tool simplicity and existence of output schema, description covers key aspects: what is searched, when to use, and return format. It mentions curation and coverage scope, providing sufficient contextual completeness.

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 already covers both query and limit with descriptions. Description adds value by listing fields matched during search (IDs, names, descriptions, etc.) and providing practical examples, enhancing understanding beyond schema.

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 clearly states it fuzzy-searches 7 curated AEMO NEM datasets, with specific verb and resource. It distinguishes from siblings like describe_dataset and list_curated by specifying the use case when exact ID is unknown.

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?

Explicitly says 'Use this when you don't know the exact dataset_id', providing clear usage context. Does not explicitly list alternatives, but the context is strong enough for an AI agent to differentiate.

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