getapi_cbs_sbi_detail

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates the HTTP method and path. It says nothing about read-only semantics (implied by GET but not stated), error behavior for unknown codes, or rate limits.

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?

Very short and front-loaded with no wasted words, but the brevity reflects under-specification rather than disciplined concision. The bracketed endpoint is the only structural element.

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, and an undocumented parameter, the definition is not complete enough for an agent to invoke the tool confidently or interpret a result. A sentence on the code format and the returned SBI record would close the 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 0% for the single required 'code' parameter, so the description must compensate. It never explains what an SBI code is, its expected format, or whether the lookup is exact-match, leaving the parameter undefined beyond its name.

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?

States a recognizable verb+resource ('SBI code lookup') and the endpoint path with a {code} path parameter, which implies a single-record detail fetch. However, it does not distinguish itself from close siblings like getapi_cbs_sbi_search or getapi_cbs_sbi, so an agent cannot tell which to pick without guessing.

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?

No when-to-use guidance, no mention of when not to use it, and no reference to the sibling lookup/search tools. The only routing hint is the {code} path shape, which is inferential rather than stated.

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