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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description contributes nothing behavioral beyond that — "client and server side from freedailypro" is not a behavioral trait. It does not say what is returned (total tip, total bill, per-person split) even though the `people` parameter implies a split mode.

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 a single short sentence, so it is not bloated, but the one clause present is wasted on branding rather than substance. Short does not equal concise when the content does not earn its place.

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 tool with an optional `people` parameter and no output schema, the description should clarify the output shape (tip amount, total, per-person split) and the effect of omitting `people`. None of this is present, and the optional-vs-required distinction is left entirely to the JSON schema.

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% and the description provides no parameter detail whatsoever. It does not explain that `bill` is the pre-tip amount, that `tipPercent` is the percentage, or — critically — whether `people` is optional and what happens when it is omitted. With three undocumented parameters and no compensating text, this is a serious gap.

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?

"Tip calculator" names the resource and the operation is inferable, so an agent can broadly tell it is a tip-computation tool. However, the phrase "client and server side from freedailypro" is branding noise that adds no distinguishing information against siblings like planning_split_bill or calculate_discount. Purpose is identifiable but vague.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative (planning_split_bill) that also handles bill splitting. The agent must infer everything about when this tool is appropriate.

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