get_kokuji

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

The description discloses the two-step retrieval process (database then fallback API), but lacks detail on output format (e.g., PDF text), error handling, or limitations—especially important since no annotations exist.

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?

Two sentences efficiently convey purpose and method. No fluff, though the structure could separate purpose from process more cleanly.

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?

The description covers purpose and retrieval logic adequately for a simple tool, but omits the return format and any prerequisites (e.g., internet access), which could confuse an 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?

The single parameter is fully described in the schema (including examples), so the description adds no extra semantic value. Baseline 3 applies due to 100% schema coverage.

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 it retrieves the full text of notifications (kokuji) delegated by the Building Standards Law, distinct from sibling tools that handle laws, articles, or 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 implies the tool is for retrieving kokuji text, but does not explicitly indicate when to use it over alternatives like get_law or search_law, nor does it provide exclusions.

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