getapi_cbs_sbi_search

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing beyond 'search'. The GET path weakly implies a read-only operation, but there is no disclosure of pagination, rate limits, matching semantics (exact vs partial), or what happens when q matches nothing.

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?

It is a single short line with no wasted words and the bracket endpoint reference is compact. The brevity is really under-specification rather than tight editing, so it is appropriately sized but not informative.

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 no annotations, no output schema, 0% parameter documentation, and two sibling tools covering the same SBI domain, the description does not supply enough for an agent to call this tool correctly or choose it over alternatives. It is essentially a name restatement plus a URL.

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 0%: both parameters are undocumented, and the schema even leaves 'limit' with no type or constraints. The description adds nothing about what 'q' should contain (SBI code fragment? description text? min length 2) or what 'limit' controls, so an agent has no basis for filling them correctly.

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 pairs a verb ('search') with a resource ('SBI code') and names the HTTP endpoint, so the general function is inferable. However, it does not explain what an SBI code is or how this differs from the sibling getapi_cbs_sbi and getapi_cbs_sbi_detail, leaving the agent to guess which of the three to pick.

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 statement of when to use this tool versus the closely related getapi_cbs_sbi and getapi_cbs_sbi_detail siblings, no prerequisites, and no mention of result limits or filtering behavior. The endpoint path is the only context provided.

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