get_tsutatsu

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

No annotations are provided, so the description carries full burden. It discloses the tool scrapes the NTA site, indicating external dependency and potential latency. However, it does not mention error handling, rate limits, idempotency, or return behavior. Partially transparent but lacking comprehensive behavioral details.

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 compact sentences in Japanese, front-loaded with the core purpose. Every sentence provides unique information. No unnecessary words or repetition.

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 tool has no output schema and the description does not explain what is returned (e.g., full text, summary, specific fields). For a scraping tool, this is a notable gap. Given the simplicity of the tool (2 required parameters, no nested objects), the description is adequate but incomplete regarding output and error conditions.

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 coverage is 100% with descriptions for both parameters. The description adds value beyond schema by clarifying that abbreviations are supported and providing mapping examples (e.g., '所基通' to '所得税基本通達'). This helps the agent understand parameter flexibility.

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 specific circulars from NTA, including support for abbreviations. It specifies the resource ('国税庁の通達') and action ('取得する'), distinguishing it from sibling tools like list_tsutatsu and search_tsutatsu.

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 usage for getting a specific circular by name and number, but provides no explicit guidelines on when to use this tool vs alternatives. Siblings are listed but not referenced. No when-not-to-use or prerequisite information.

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