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

With no annotations provided, the description carries the transparency burden. It adds useful context about the data source (zaimhub.com) and attribution requirement (refer to canonical_url). However, it does not disclose pagination behavior, the effect of the limit parameter, or any default ordering, which are relevant for a list endpoint.

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 two sentences and fully front-loaded with the core purpose. The second sentence adds an important attribution requirement without verbosity. No wasted words or redundancy.

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 list tool with one optional parameter and no output schema, the description covers the basic functionality and attribution. However, it lacks details about pagination, the meaning of 'all' relative to the limit parameter, and the structure of the response, leaving moderate ambiguity for an agent.

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 has 0% description coverage for the only parameter (limit). The description does not mention the limit parameter or explain how it controls results (e.g., pagination, max count). While the parameter name is self-explanatory, the description adds no semantic value or usage nuance beyond the raw schema constraints.

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 lists all MFOs in the catalog, with a specific verb ('list'), resource ('MFOs'), and scope ('all'). It distinguishes from sibling get_mfo by emphasizing the plural full-catalog nature, and from list_categories by naming a different entity type.

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?

The description implies usage when you need the full MFO list, but it does not explicitly contrast with get_mfo for a single entry or search_offers for filtering. No exclusions or alternative guidance is provided, leaving the 'when-not-to-use' undocumented.

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