advise_technique

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

With no annotations, the description carries the full burden of disclosing behavior. It reveals the 'keyword analysis' mechanism, but does not mention limitations, what kind of descriptions work well, or how recommendations are produced beyond keyword matching. No contradiction with annotations exists because none were provided.

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 no filler and front-loads the core action. It is concise, though it sacrifices detail that could have been included without bloating the text.

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 one-parameter tool with an output schema, the basic purpose is present, but the definition lacks usage guidance and parameter semantics. An agent would still need to infer what kind of description to provide and when to choose advise_technique over sibling tools.

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 0%: the only parameter, 'description', has just a title and no schema description. The tool description mentions 'described testing context' but fails to specify expected content, format, length, or examples, so it does not compensate for the schema gap.

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 states a specific verb ('Recommend'), resource ('techniques and heuristics'), and context ('described testing context via keyword analysis'). It is clear in what it does, though it does not explicitly differentiate itself from sibling tools like catalog_techniques or catalog_heuristics.

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?

There is no guidance on when to use this tool versus siblings. The phrase 'for a described testing context' implies a use case, but there are no explicit conditions, exclusions, or alternatives such as catalog_techniques for browsing all techniques.

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