조달업체 프로파일 조회

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

Annotations indicate readOnlyHint=true (read-only) and openWorldHint=true. Description adds that lists may be truncated due to query limits and that each call consumes at least 4 API requests per facet, providing critical behavioral info 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?

Three efficient sentences: first states purpose, second gives usage guidance, third provides behavioral constraints. Every sentence earns its place with no 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?

For a tool that assembles multiple facets with no output schema, the description covers purpose, usage, parameters, limitations, and cost. It is complete given the complexity and annotations.

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 has 100% parameter coverage with pattern and required. Description adds that business number is mandatory and no resolver exists, but this only marginally improves understanding beyond the schema.

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?

Description clearly states it assembles and returns basic info, business types, supplied goods, and sanctions for a procurement company using a business registration number. It distinguishes from sibling tool check_company_qualification by scope.

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?

Explicitly advises when to use (for an overall company overview) and when not (use check_company_qualification for checking specific qualifications). Notes that business number input is mandatory and there is no company-name resolver.

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