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

No annotations are available, so the description carries the full burden of behavioral disclosure. It only notes that it is a 'browser-based tool' but does not explain whether it provides estimates, requires user inputs, or what the output represents. The lack of details on limitations or how the calculation works leaves the agent with significant ambiguity.

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 a single, front-loaded sentence that efficiently conveys the core functionality. Every word is necessary, and there is no redundant 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?

The description lists the tax categories but does not explicitly state what the tool outputs (e.g., take-home pay after deductions). Since there is no output schema, the description should clarify the result. The title 'フリーランス手取りシミュレーター' partially compensates by implying the output, but the description itself lacks explicit output details.

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?

Since the tool has zero parameters, the baseline score is 4. The empty input schema clearly signals no parameters, and the description adds no additional parameter information, which is unnecessary in this case.

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 states a specific verb ('calculates') and lists the exact tax types (income, resident, business, national health insurance, pension, consumption tax) for freelancers. This distinguishes it from sibling tools that focus on a single tax type, making its purpose unambiguous.

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 use for comprehensive freelancer tax calculation through the phrase '全て計算' (calculates all), but it does not explicitly mention when to choose this over alternatives such as resident-tax-calc or tax-return-calc. No exclusions or alternative references are provided, so guidance is only implicit.

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