find_reusable_test_cases

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

With no annotations, the description carries full burden but mentions nothing about behavior (e.g., read-only, destructive, auth needs). The tool might be a read operation, but that is not stated, making it unsafe for the agent to use.

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 short sentence, which is under-specification rather than conciseness. It fails to convey essential information given the tool has 3 parameters and no other structured documentation.

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?

The tool lacks output schema, parameter descriptions, and behavioral information. For a search/find operation with multiple filters, the description should provide details on expected returns, but it provides none.

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 input schema has 0% parameter description coverage, and the description does not explain what 'ticket_id', 'filter_tags', or 'filter_priority' mean or how they affect results. The agent gets no semantic help beyond the parameter names.

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 'Find existing test cases for reuse' provides a general idea but lacks specificity. It doesn't differentiate from siblings like 'save_test_cases' or 'create_test_case' which could also involve existing cases. The purpose is vague, not clearly indicating the scope or distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about what scenarios this tool is appropriate for, leaving the agent without decision support.

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