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

With no annotations, the description carries the full behavioral burden. It discloses that this is a third-party paid service, that cc0.company pays an upstream x402 client and adds a commission, and that the buyer pays $0.02 USDC per call. It omits error/rate-limit details, but for a simple query tool the key non-obvious behavior (payment) is transparent.

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 reasonably front-loaded with purpose and usage, but the third-party commission sentence is verbose and partly redundant with the later '[PAID: $0.02 USDC per call via x402]' tag. The main point could be made more compactly without losing critical information.

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?

Given the tool has a single parameter and no output schema, the description states the return type ('matching lore excerpts'), the input semantics, and the pricing. It is sufficient for correct invocation; minor gaps such as result format or pagination limits are not critical for a simple query service.

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 only describes 'prompt' as 'Input prompt for this service,' which is generic. The description adds meaning by instructing 'Pass your search as the prompt,' clarifying that the single parameter should contain the search query. This goes beyond the schema's minimal description.

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 uses a specific verb and resource: 'Query the mfer lore archive (history, culture, community)' and states it returns 'matching lore excerpts.' This clearly distinguishes it from sibling tools like mfergpt-ask by naming the unique archive.

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?

It gives a clear usage instruction: 'Pass your search as the prompt,' and the opening phrase establishes the intended use case for lore/history/culture/community queries. It does not explicitly name alternatives or exclusions, but the context is clear.

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