list_capabilities

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

With no annotations provided, the description carries full behavioral disclosure. It states the tool is free, always reads the live /openapi.json (never stale), and describes the two invocation modes. It does not disclose rate limits, pagination, or the exact response structure, but for a read-only catalog that is largely sufficient.

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 front-loaded with 'FREE — no wallet needed' and the core verb. The long parenthetical enumeration of categories is verbose but provides valuable scope information. Every sentence contributes, though the category list could be trimmed without losing essential function.

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 tool with one optional parameter and no output schema, the description covers cost, live data behavior, both invocation modes, and category examples. It does not address error cases, response format, or limits, but the core decision-making information is present.

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 already fully describes the optional 'category' parameter with examples ('math', 'vision'). The description adds that passing a category lists every route with price and description, but this is more behavioral context than parameter semantics. Since schema coverage is 100%, a baseline 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 states a specific action (browse the ForgeMesh Utility Grid catalog) and clearly differentiates from siblings by explicitly offering two modes: a category overview with no arguments, or listing routes in a category. This distinguishes it from search_capabilities and get_endpoint_spec.

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 provides clear usage context: no arguments yields a category overview with route counts; passing a category yields routes with price and description. It also notes the data source is live. However, it does not explicitly state when not to use this tool or point to alternatives like search_capabilities for its exclusion.

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