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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds no behavioral context of its own — no mention of rounding behavior, currency assumptions, or what the calculation returns — and 'client and server side' conveys nothing actionable.

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?

It is one sentence, but a meaningful fraction of it ('client and server side from freedailypro') is filler that does not earn its place. The useful fragment is not front-loaded or expanded, so brevity here reflects under-specification rather than economy.

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?

For a 3-parameter calculator with no output schema and zero schema documentation, the description should state the formula intent (per-person amount, tip handling, rounding) and return shape. None of that is present, leaving the agent to guess how 'total', 'people' and 'tipPct' combine.

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 description coverage is 0%, so the description must carry parameter meaning, and it does not: 'total', 'people' and the optional 'tipPct' are never explained, nor are units, currency, or whether tip is a percentage (0-100) or a fraction. Only the generic word 'bill' hints at 'total'.

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 phrase 'Split bill calculator' identifies the resource and operation, so an agent can broadly tell what it does. However, the trailing 'client and server side from freedailypro' is unexplained vendor/implementation noise that dilutes the purpose, and nothing distinguishes it from the adjacent calculate_tip or planning_event_budget siblings.

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?

There is no guidance on when to use this versus alternatives such as calculate_tip or planning_monthly_budget, and no stated prerequisites. The agent is left to infer usage entirely from the name.

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