TestDino MCP

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

With no annotations provided, the description carries full burden and does well by disclosing batch operation limits (max 20), the types of information returned (statistics, suites, git metadata, errors), and the tool's purpose for analysis/debugging. It doesn't cover rate limits or authentication needs, but provides solid behavioral context.

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 that are front-loaded with core functionality and usage guidance. Every sentence earns its place: first describes what the tool does, second provides usage context and batch operation details. No wasted words.

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 read operation with no annotations and no output schema, the description provides good context about what information is returned and how to use it. It could be more complete by specifying the return format or pagination, but covers the essential aspects well given the tool's complexity.

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%, so the baseline is 3. The description adds value by mentioning batch operations (comma-separated IDs, max 20), which aligns with the 'testrun_id' parameter, but doesn't provide additional semantic context beyond what the schema already documents for parameters.

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 verb ('Get detailed information') and resource ('about test runs'), specifying what information is retrieved (test statistics, test suites/cases, git metadata, error details). It distinguishes from siblings like 'list_testruns' by focusing on detailed analysis rather than listing.

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?

Explicitly states when to use this tool ('to analyze test execution health or debug specific failures') and includes practical guidance on batch operations (comma-separated IDs, max 20). It differentiates from 'list_testruns' by emphasizing detailed analysis over listing.

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