search_dataset

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the DSORG filter and result capping, both of which restate schema content; it says nothing about catalog scope, latency, or what happens when no datasets match.

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 no filler, and the core action is front-loaded. It is appropriately sized, though the second sentence is largely redundant with the schema.

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 4 fully documented parameters and no output schema, the description should still convey what a result looks like (dataset names vs. full attributes) and how capping behaves. It hints at capping but leaves the return shape and empty-result behavior unstated, so the agent is left with a gap.

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 all four parameters are documented in the schema with examples and an enum. The description restates the wildcard and DSORG concepts without adding syntax or format detail beyond what the schema already provides, so the 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 states a specific verb (Search) and resource (catalog for datasets) plus the matching mechanism (wildcard pattern). It is clear what the tool does, but it does not distinguish itself from adjacent siblings like list_datasets, get_dataset_info, or search_members, leaving the agent to infer the boundary.

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?

Usage is only implied by 'Search the catalog ... matching a wildcard pattern' and 'Supports DSORG filter'. There is no explicit when-to-use guidance, no mention of alternatives like list_datasets, and no stated prerequisites (e.g., environment must exist).

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