TestDino MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the tool 'creates' a new manual test case, it lacks details on permissions required, whether the operation is idempotent, error handling, or what the response looks like (e.g., success confirmation or created ID). For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is front-loaded with the core purpose in the first sentence, followed by supporting details in a second sentence. Every sentence adds value by explaining usage context and supported features without redundancy or unnecessary elaboration, making it efficient and well-structured.

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?

Given the complexity of 12 parameters (with 5 enums) and no output schema or annotations, the description is adequate but incomplete. It covers the purpose and basic usage but lacks behavioral details (e.g., response format, error cases) and deeper parameter guidance. For a creation tool with many parameters, more context would be beneficial, though it meets minimum viability.

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?

The description adds some value by listing the types of metadata supported (priority, severity, type) and content (test steps, preconditions, postconditions), but the input schema already has 100% description coverage with detailed parameter documentation. The description does not provide additional syntax, format, or usage examples beyond what the schema specifies, so it meets the baseline for high schema coverage.

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 specific action ('Create a new manual test case') and resource ('manual test case'), distinguishing it from siblings like 'create_manual_test_suite' (which creates suites) and 'update_manual_test_case' (which modifies existing cases). It also mentions the types of content that can be added (test steps, preconditions, etc.), providing a comprehensive overview of its function.

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?

The description provides clear context for when to use this tool ('to document new test scenarios, features, or requirements'), but it does not explicitly state when not to use it or name alternatives. For example, it doesn't clarify that 'update_manual_test_case' should be used for modifications instead. However, the guidance is sufficient for basic usage.

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