bcrp_search_catalog

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

No annotations are present, so the description carries the full burden. It states what is returned — series codes, names, descriptions, frequency, units, and period format — and how that output connects to bcrp_get_series. It does not discuss result limits or matching semantics, but the disclosed scope is solid.

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?

The description is front-loaded with the purpose and return value, followed by a compact list of useful examples and a cross-reference to a related tool. Every sentence and bullet earns its place without digression.

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?

For a three-parameter search tool with no output schema, the description explains the return fields, provides representative queries, and points to the relevant sibling tool for category browsing. It is sufficiently complete for an agent to invoke it correctly, though it leaves minor details like result limits unstated.

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 the baseline for parameter semantics is 3. The description adds example query intents, but does not substantially extend the parameter meaning beyond what the schema already documents.

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 opens with a specific verb and resource: 'Search the built-in catalog of important BCRP series by keyword.' It also lists the exact fields returned, clearly distinguishing it from sibling tools such as bcrp_list_catalog_categories and bcrp_get_series.

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?

Provides clear usage context via example queries and explicitly routes the agent to bcrp_list_catalog_categories to explore categories. It does not explicitly state an alternative for when a series code is already known, but the search intent is clear.

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