yaaif_mcp_tools_list

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the operation. It does not mention read-only safety, pagination behavior, or result format. The verb 'List' implies a read operation, but no explicit behavioral traits are disclosed.

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 a single, front-loaded sentence with zero filler. It immediately conveys the tool's purpose, making it easy for an agent to parse. Conciseness is appropriate for a simple list operation.

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?

The description is too sparse for an agent to fully invoke the tool correctly. It leaves the meaning of q and limit unspecified, and with no annotations or output schema, the agent lacks information about expected return values. The tool is simple, but the description still has clear gaps.

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 two parameters (q and limit) with 0% description coverage, and the description does not mention either. An agent cannot infer what 'q' filters on or how 'limit' behaves. The description provides no compensation for the missing schema descriptions.

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 uses a specific verb ('List') with a clear resource ('external MCP tools') and scope ('tenant catalog'). This distinguishes it from sibling tools like yaaif_local_tools_list (local tools) and yaaif_mcp_servers_list (servers, not tools).

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 gives no guidance on when to use this tool versus alternatives such as yaaif_mcp_tool_get or yaaif_local_tools_list. There are no exclusions, conditions, or alternative routing hints. The context is clear but the description fails to help an agent choose correctly among many similar list tools.

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