calculate_slope

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

No annotations are present, so the description must convey behavior. It mentions return values (slope%, angle°) but lacks details on side-effects, permissions, or limitations. For a calculation tool, this is acceptable but minimal.

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?

Three focused sentences with no wasted words. Front-loaded with action and outputs, then use context, and a pointer to related tools.

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?

While an output schema exists (not shown), the description covers inputs, outputs, and use cases. A minor inconsistency: it claims to return 'ratio' but later lists only slope% and angle°. Missing error conditions for non-positive run, but schema enforces minimum.

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%, so baseline is 3. The description restates 'Inputs: rise, run' but adds no new detail beyond the schema descriptions. Minor value from context hinting at meters.

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 specifies 'Compute slope as percentage, angle in degrees, and ratio' and provides concrete use cases (ramps, roofs, terrain analysis), making the tool's purpose distinct from siblings like calculate_drain_slope.

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?

It states when to use (ramps, roofs, terrain analysis) and references list_bundles for related calculators, but does not explicitly exclude cases or name alternative tools.

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