makiti_guide

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

With no annotations available, the description carries the full burden of behavioral disclosure. It states the tool 'gets guidance' but does not describe the output format, whether it calls other tools, or any side effects. This lack of information leaves the agent uncertain about the tool's actual behavior.

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, well-structured sentence that front-loads the primary purpose with no redundant words. It efficiently communicates the tool's function without unnecessary elaboration.

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 description gives the essential purpose but lacks details about what the guidance output looks like or how it interacts with sibling tools. Given the absence of an output schema and annotations, the description is minimally sufficient but leaves ambiguity about the tool's actual deliverable.

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 provides 100% coverage for the single 'scenario' parameter, including a description and example. The tool description itself adds no parameter-specific information, but since the schema is self-explanatory, the baseline score of 3 is appropriate.

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 tool provides guidance on using Makiti tools for shopping decisions, with a specific verb ('Get guidance') and resource ('how to use Makiti tools'). This distinguishes it from sibling tools which directly perform shopping actions like search, compare, or find prices.

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 the sibling tools. There is no mention of alternatives, exclusions, or specific scenarios that would trigger its use. The description only implies a purpose without contextual usage direction.

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