Query test data

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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description contributes the important constraint that matching is exact field values only, but says nothing about pagination, ordering, or what happens when no rows match.

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?

A single front-loaded sentence with zero filler; the resource comes first and the filtering constraint follows. Nothing is padded or repeated from the title.

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 tool with a nested-object filter parameter and no output schema, the description leaves real gaps: whether filters AND together, whether only string equality is supported (no ranges or operators), and whether results are bounded by limit. Adequate as a minimal definition but not complete.

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 67% with entity and filter documented, and the description usefully reinforces that filter works on exact values (consistent with the string-only additionalProperties). The 'limit' parameter is undocumented in both schema and description, so the description doesn't fully compensate.

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?

States a specific verb ('look up') and resource ('test accounts, products or other fixtures'), and adds the query model ('filtered by exact field values'). The resource is clearly distinct from the sibling tools (suites, runs, results, bugs), though no sibling is named explicitly.

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?

Usage is implied: exact-match filtering over fixtures, not running or inspecting tests. There is no explicit when-to-use/when-not guidance and no pointer to a sibling for related needs (e.g. get_test_results for actual outcomes).

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