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

With no annotations, the description carries full behavioral burden. It usefully flags 'FREE' (cost) and enumerates the payload contents including key scope and key cost, but says nothing about authentication requirements, output format, or pagination for a potentially broad directory.

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?

Front-loaded with the most decision-relevant token ('FREE') followed by a single dense sentence and a routing hint. No wasted sentences, though the middle clause is list-heavy.

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 no-parameter, no-output-schema discovery tool, the description enumerates what comes back (URL, tools, prices, free tier, key scope, key costs) well enough for an agent to know it should call this first. Only the lack of auth/format detail keeps it from a 5.

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?

Zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it does not need to.

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 the resource precisely: a directory of every AIS MCP building with URL, tools, prices, free tier and key scope. This clearly separates it from siblings like about_aislabs and how_to_pay, though the verb is implicit (no explicit 'list'/'retrieve').

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?

'Start here.' gives a clear implied entry-point cue, but it never names the sibling tools or states when this should be used instead of about_aislabs or how_to_pay. Usage is implied rather than specified.

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