공고 개찰 상세

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

Beyond annotations (readOnlyHint, openWorldHint), the description discloses that unspecified bidKind/status can consume up to 15 API requests internally, how multi-category/round results are handled, and that award method is estimated (with details on scoring). This adds significant 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 well-structured and front-loaded with purpose, but slightly lengthy due to detailed behavioral notes. Every sentence adds value, though some condensing is possible.

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 the tool's complexity (7 parameters, no output schema, internal API behavior), the description covers all key aspects: usage context, parameter effects, alternatives, and transparency on internal requests. No significant gaps.

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?

With 100% schema coverage, the description adds crucial context: myBizno marks isOurs flag, bidKind/status affect API consumption, and specific values reduce traffic. It explains trade-offs beyond schema descriptions.

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 tool retrieves a single bid result record by bid announcement number, using composite key matching, and lists the specific data fields. It explicitly distinguishes from sibling tools search_awards and search_openings for multi-announcement searches.

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 explicit when-to-use (single bid lookup for post-analysis) and when-not-to-use (multiple announcements: use siblings). It also advises specifying bidKind and status to reduce API calls, offering efficiency guidance.

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