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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that the result is a 0-100 score; it says nothing about scoring weights, assumptions, or failure behavior. Nothing contradicts the annotations.

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 sentences, front-loaded with the purpose and inputs, and the output range immediately follows. The trailing promotional link to an external calculator page is the one element that does not strictly earn its place, but it does not obscure the key 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?

With no output schema, the description correctly states the return shape (0-100 score), which is the main thing an agent needs to know. It is reasonably complete for a simple scoring tool, though it does not explain whether higher scores mean more or less friction, which could affect interpretation.

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 100% with enum descriptions for every parameter, so the schema carries the meaning. The description merely restates the same five inputs without adding format or weighting detail, leaving the baseline 3 appropriate.

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?

States a concrete verb (Score) and resource (a mobile checkout flow's friction), enumerates the five input factors, and names the output shape (0-100 score). It is specific enough to distinguish from generic siblings, but it never names the closely-related alternatives (e.g. friction_point_identifier, form_field_friction_cost_calculator) it could be confused with.

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 exclusions, and no named alternatives despite a large sibling set of similar friction/checkout calculators. The agent must infer applicability purely from the tool name.

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