mh_tool

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

Discloses that it uses pre-generated answers, does not invoke the LLM, and returns near-instantly, which is key behavioral context. With no annotations, this is the primary source of behavioral information, though it does not cover failure modes or side effects of force_refresh.

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 longer than typical but front-loads the core purpose and includes structured examples and bolded guidance. Every sentence serves a purpose, though it could be tightened.

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 simple two-parameter retrieval tool, the description covers purpose, usage, and discovery guidance. It lacks output format details, but that is acceptable given no output schema and the simplicity of the 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?

The schema already describes both parameters with 100% coverage, so the description adds little beyond the example name. It does not clarify semantics further than the schema does.

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 identifies the tool as a caller for pre-generated answers, with a specific resource (standard questions) and distinguishes it from mh_search. It lists concrete categories, making the purpose unmistakable.

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?

Explicitly instructs to use this tool for standard questions first, forbids using mh_search instead, and directs to mh_tools_list for discovery. Provides both positive and negative usage guidance.

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