get_slow_tests

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the tool shows stats but doesn't disclose that it is a read operation, authentication needs, or pagination behavior. No mention of side effects.

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?

One clear, front-loaded sentence that efficiently conveys purpose. Could be slightly more structured by listing stats, but it's concise and scannable.

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?

No output schema, so the description partially compensates by mentioning stats. However, it lacks specifics on return structure. Parameter details are covered by schema, but overall context for a 4-parameter tool (2 required) is adequate.

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 references the duration threshold and stats but adds no extra meaning beyond the schema's parameter descriptions (limit, threshold_ms). Not detrimental, but not additive.

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 states the tool finds tests exceeding a duration threshold and specifies what stats are shown (percentage, average duration). It distinguishes from siblings like get_failed_tests. The verb 'Find' and resource 'tests exceeding a duration threshold' are specific.

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?

No explicit guidance on when to use vs alternatives. With many sibling test-related tools (e.g., get_failed_tests, get_flaky_tests), a statement about when to choose this tool is missing.

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