find_practitioner_for_auction

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

With no annotations, the description carries the full burden and does well: it discloses the return cardinality ('2-3 practitioner federation directories'), the information-only nature, the default stage, and stage-specific legal context such as 司法書士 being almost legally required. It falls short of describing the exact result structure or edge cases like no results found.

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 dense but efficient: it front-loads the purpose, packs the stage list with meanings, and adds a crucial sibling-disambiguation warning in a single compact paragraph. Slightly verbose due to bilingual repetition, but every sentence contributes useful information.

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 no output schema and no annotations, the description compensates by explaining return count, stage contexts, legal implications, and the distinction from a related tool. It does not clarify the exact output fields or how the optional prefecture parameter affects results, which leaves minor ambiguity for the agent.

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?

Although the schema already covers all three parameters, the description adds substantial meaning to the 'stage' enum by explaining each value in domain terms (e.g., post_acquisition means ownership transfer registration, eviction means 明渡し・強制執行). It also clarifies the default behavior, going well beyond the raw 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?

The description clearly states the tool returns practitioner federation directories for auction-related stages and lists the specific professions (司法書士, 弁護士, 不動産鑑定士, 土地家屋調査士). It distinguishes from the sibling 'find_practitioner' by its auction context and explicitly warns against combining outputs.

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?

It explicitly enumerates the four stages and their use cases, provides a default stage, and gives a clear when-not instruction ('Do not combine the result of this tool with output from find_practitioner'). It also clarifies the tool is information-only, not a paid intermediary, which helps the agent set expectations.

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