houjin_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds a useful behavioral detail about matching both Japanese and registered English names, but does not disclose return format, pagination, or other behavioral traits. It provides moderate value beyond annotations.

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 a single, front-loaded sentence that immediately states the tool's purpose. It is concise with no wasted words, and the key information is easily scannable.

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 search tool with good annotations and well-documented schema, the description provides sufficient context. It does not explain what the response looks like (no output schema), but for a search tool the agent can reasonably expect a list of matches. The absence of explicit return details is a minor gap given the tool's simplicity.

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 is 3. The description adds semantic value by explicitly mentioning that name matches Japanese and registered English names, which is not captured in the schema's parameter description for 'name'. This helps the agent understand acceptable inputs for the name parameter.

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 clearly states the verb 'Search' and the resource 'Japanese corporate registry', and specifies search criteria ('by trade name and/or location'). This distinguishes it from sibling tools like houjin_corporation, which likely retrieves a specific corporation, and houjin_verify, which verifies.

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 clear context for when to use this tool: searching by trade name and/or location. It does not explicitly mention alternatives or when not to use it, but the criteria are sufficiently clear. The mention of 'Japanese and registered English names' further guides usage.

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