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

With no annotations, the description carries the full burden and delivers unusually rich behavior: third-party re-brokering via x402, a commission of max(5%, 0.005 USDC) paid to the upstream, and the buyer_price_usdc the caller pays. It omits auth requirements, rate limits, or failure modes, keeping it short of a 5.

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?

Purpose is front-loaded in the first sentence, followed by return behavior, then payment mechanics. The commission sentence is dense and slightly legalistic, but no sentence is truly redundant given the paid nature of the call.

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 no output schema and no annotations, the description covers purpose, return shape ('lore excerpts'), and the critical cost/payment model. It is nearly complete; only auth and error behavior are absent.

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 100% for the single 'prompt' parameter, so the baseline is 3. The description only restates 'Pass your search as the prompt', adding no syntax, format, or length guidance beyond the schema.

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?

States a specific verb and resource ('Query the mfer lore archive (history, culture, community)') and what it returns ('matching lore excerpts'). It is clear on its own, but never distinguishes itself from close siblings like mfergpt-ask or mfergpt-mferfy, so an agent must guess which mfergpt tool fits.

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 when-to-use versus when-not guidance and no named alternative among the many siblings. The only contextual cue is the price line, which tells the agent it costs $0.025 USDC but not when this search is the right choice.

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