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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered by structured data. The description adds only the constraint 'Run must be above zero', which is a useful but minimal behavioral note and says nothing about error behavior or units. With annotations carrying the safety profile, a 3 is appropriate.

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 short sentences, zero filler, with the core function and the output formats front-loaded and the single constraint last. Nothing in it is redundant padding.

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?

There is no output schema, but the description names the return values (degrees, percent grade, ratio), which is the key missing piece an agent would otherwise have to guess. For a two-parameter, side-effect-free calculator this is nearly sufficient; only unit conventions and failure behavior on run <= 0 remain unstated.

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 coverage is 100% and both parameters are documented ('Horizontal run, above zero', 'Vertical rise'), so the baseline is 3. The description's 'Run must be above zero' merely restates the schema's own constraint and adds no new semantic detail such as units or accepted ranges.

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 specific verb and resource ('Compute slope from rise and run') and enumerates the three output formats (degrees, percent grade, rise-to-run ratio), which goes beyond a bare name. No sibling tool covers slopes or angles, so sibling differentiation is moot rather than achieved.

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?

Usage is implied: an agent with a rise and a run can infer this is the right tool, and no competing sibling exists to route away from. However, there is no explicit when-to-use statement or pointer to any alternative (e.g., for hypotenuse/length questions).

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