get_test_cases_advanced

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'advanced retrieval with filtering and pagination' which implies read-only behavior, but doesn't explicitly state whether this is a read operation, what permissions might be required, rate limits, or what the return format looks like. The description adds some context about suite filtering but lacks comprehensive behavioral details.

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 efficiently structured with emoji icons and clear sections (purpose, important notes, tip). While slightly verbose with the emoji decorations, every sentence earns its place by providing distinct value. The information is front-loaded with the core purpose stated first.

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 complex tool with 13 parameters and no output schema, the description provides adequate context about filtering capabilities and sibling alternatives. However, it doesn't describe the return format, pagination behavior, or error conditions. With no annotations and no output schema, more comprehensive behavioral context would be helpful for this advanced retrieval tool.

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 schema already documents all 13 parameters thoroughly. The description adds minimal parameter semantics beyond what's in the schema - it only clarifies the suite_id vs root_suite_id distinction. This meets the baseline expectation when schema coverage is high.

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's purpose as 'Advanced test case retrieval with filtering and pagination' with specific enhancements mentioned (automation state and date filtering). It distinguishes itself from basic retrieval tools but doesn't explicitly differentiate from all sibling tools beyond the one mentioned alternative.

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 explicit guidance on when to use this tool vs alternatives: it specifies to use 'suite_id' for direct parent suites and 'root_suite_id' for root suites, and explicitly recommends using 'get_test_cases_by_suite_smart' for automatic suite type detection. This gives clear when/when-not/alternative instructions.

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