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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact, 'Cursor-paginated,' which is not encoded in any annotation. It stops short of disclosing rate limits, result caps, or what the catalog returns beyond metadata.

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 no filler, and the resource scope is front-loaded before the pagination note. It is borderline undersized for a 7-parameter tool, but nothing present is wasted.

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 0 required parameters, an 86%-covered schema, and annotations carrying the full safety profile, the description covers just enough to call the tool. It omits pagination loop guidance, the default page size behavior, and any note on how sorted results are ordered, which would be useful for a search endpoint.

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 86%, so the schema already documents q, cursor, keyword, org_slug, org_type and per_page bounds. The description reinforces pagination via 'Cursor-paginated' but adds no format or interaction detail (e.g. how sort interacts with q) beyond the 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?

Specific verb ('Search') plus a named resource ('the Data.gov catalog') and an explicit content scope ('dataset metadata from federal, state, local and tribal publishers'). It is reasonably distinguishable from siblings like datamart_search or loc_search, though it never states that distinction.

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?

There is no when-to-use or when-not-to-use guidance and no reference to any alternative search tool. The only usage signal is implicit in the phrase 'Search the Data.gov catalog,' leaving routing decisions to the reader.

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