search_bkp_codes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'search' without revealing if the operation is read-only, what the output format is, or any constraints like authentication or rate limits. The minimal description lacks necessary behavioral context.

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 one sentence, no wasted words, and front-loaded with the verb 'Search' and resource 'BKP codes'. It efficiently conveys the core purpose without redundancy.

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 no output schema, the description should hint at return values or behavior, but it does not. The tool is a search with two parameters, yet the description lacks information about result format, pagination, or number of results. This deficiency leaves the agent underinformed.

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 schema already documents both parameters ('query', 'lang') with descriptions. The description adds no new information about parameter semantics; it simply paraphrases the schema's 'Search term (keyword or code number)' for query. Baseline of 3 is appropriate.

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 the tool searches BKP codes by keyword or number, clearly identifying the resource and action. It distinguishes from siblings like browse_bkp_tree (browsing) and search_cpv_codes (different domain). However, it does not explain what BKP codes are, which could further clarify the purpose.

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 description provides no guidance on when to use this tool compared to alternatives such as browse_bkp_tree or other search tools. There is no explicit 'when to use' or 'when not to use' information, leaving the agent to infer usage context.

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