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

With no annotations provided, the description carries the full burden. It clearly implies a read-only operation by using 'List', but it does not disclose any additional behavioral traits such as response format, potential pagination, or effects on resources. For a simple listing tool, this minimal disclosure is acceptable but not exceptional, hence a middle score.

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 with zero filler. The core purpose and the included resource types are front-loaded, and the parameter note is concise. Every word earns its place, making it highly efficient.

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 simplicity of the tool (no parameters, no output schema), the description provides a solid list of what will be returned (resource categories) but does not specify the format of the output (e.g., whether it's a list of URLs, brief descriptions, or a structured object). An agent might benefit from a hint about the structure or the nature of the items, so completeness is adequate but not fully robust.

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 the description explicitly notes 'No arguments.' Per the rubric, a zero-parameter tool gets a baseline of 4 because there is nothing to explain beyond the absence of inputs. The description does not need to add parameter semantics.

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 verb ('List'), a clear resource ('official aicoolies developer resources'), and enumerates the exact types (OpenAPI, MCP, llms.txt, datasets, developer portal). It clearly distinguishes itself from sibling tools like get_tool or search_tools, which focus on individual catalog entries rather than a bundled resource overview.

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 implicitly indicates when to use this tool (when you want a listing of developer resources) but does not explicitly state when not to use it or mention alternatives. There is no guidance contrasting it with get_catalog_meta or search_tools, leaving the agent to infer usage context from the tool name and purpose.

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