Catalogue and prices (free)

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully adds that the call is free with no payment required and that it reports wallet configuration status. However, it doesn't explicitly state that the operation has no side effects, and without an output schema it doesn't describe the return structure beyond content items.

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?

Three short sentences deliver the full function, the cost, and the recommended call timing in order of importance. The only redundancy is 'Free — no payment required' repeating the title's '(free)', but it reinforces a decision-relevant fact and earns its place.

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 complexity of zero parameters, no output schema, and no annotations, the description is nearly complete: it defines the result content (tools, prices, schemas, wallet status) and gives the key routing instruction. The only missing piece is the exact return format, which is a minor gap for a no-argument listing call.

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 tool has zero parameters and schema coverage is 100%, so the baseline of 4 applies. The description correctly reflects this by referring to a single implicit input (the session) and focusing on what the call returns rather than argument handling.

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 names a specific verb ('List') and a precise resource ('every tool this service offers'), and enumerates exactly what is returned: price, input schema, and wallet status. This clearly distinguishes it from sibling content-processing tools like farm_clean_text and farm_jsonld, which have entirely different purposes.

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?

'Call this before paying for anything' is explicit, actionable timing guidance that tells an agent exactly when this tool is the right choice. No when-not-to-use or alternative routing is given, but none of the siblings are remotely similar to a catalog function, so no contrast is needed.

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