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

With no annotations, the description must carry the full burden of behavioral disclosure. It only notes the tool is browser-based and performs auto social insurance calculation, but does not explain how it works, what output it produces, or any side effects. Behavior is largely opaque.

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 extremely brief, consisting of a single phrase plus a parenthetical. It is concise and front-loaded with the main function, though it is perhaps too sparse. For a simple tool, the length is appropriate.

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 has no parameters, no annotations, and no output schema, the description should provide a fuller picture. It does not specify the output format, how the tool is invoked, or what data it needs. The browser-based note is helpful but insufficient for an agent to understand the tool's full behavior.

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 input schema is empty (0 parameters), so the baseline is 4. The description does not need to clarify parameter meanings, but the mention of 'auto social insurance calculation' implies the tool computes values automatically without requiring user-supplied parameters.

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 identifies the tool as generating payslips and highlights the auto social insurance calculation feature. It does not explicitly distinguish from sibling tools like social-insurance-calc or take-home-pay-calc, but the function is 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?

No guidance is given on when to use this tool instead of alternatives. There is no mention of related calculation tools, no prerequisites, and no typical use case beyond the bare function. The description leaves usage entirely to inference.

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