te_get_policy_test_results

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

No annotations are provided, so the description bears full responsibility for behavioral traits. It only says 'Search', implying read-only, but does not explicitly state it is non-destructive, lacks rate limit info, authentication needs, or any side effects. This is inadequate for an agent to understand operational impact.

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 a single sentence with a list of filters, front-loaded with the purpose. No extraneous information; it is efficient and well-structured for quick reading.

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 3 parameters, no output schema, and no required fields, the description should explain return values and all parameters. It only partially covers filters and omits explanation of 'raw' and 'latest'. No mention of output format or pagination behavior, leaving the tool usage incomplete.

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 0%, so the description must compensate. It adds meaning to the 'filters' parameter by listing common fields (nodeId, state, policyTestName, paging), but does not explain 'raw' and 'latest' parameters. This provides partial value but leaves gaps.

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 'Search' and resource 'policy test results', and lists specific filter fields (nodeId, state, policyTestName) which add detail. However, it does not differentiate from sibling tools like te_get_policy_test_result (singular) or te_get_node, so clarity is good but not exceptional.

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 mentions 'Use filters for...' but provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context. There is no when/when-not distinction, making it insufficient for guiding tool selection.

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