insp_resources_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'lists' resources, implying a read-only operation, but doesn't cover aspects like whether it requires authentication, how it handles errors, if it's rate-limited, or what the output format looks like (e.g., JSON list). This leaves significant gaps for an agent to understand its behavior.

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, clear sentence that front-loads the core purpose without unnecessary words. It efficiently conveys the essential information, making it easy for an agent to parse quickly.

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 complexity (5 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain what 'resources' entail in this context, how results are returned, or any behavioral traits like error handling. For a tool that likely inspects server capabilities, more context is needed to guide effective use.

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 has 100% description coverage, so parameters are well-documented in the schema itself. The description adds no additional meaning about parameters beyond implying the tool interacts with an MCP server, which is already inferred from the schema's command/args/url fields. This meets the baseline for high schema coverage.

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 action ('List all resources') and the target ('exposed by an MCP server'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'insp_resources_read' or 'insp_resources_templates', which likely have different purposes related to resources.

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 no guidance on when to use this tool versus alternatives. With siblings like 'insp_resources_read' (likely for reading a specific resource) and 'insp_resources_templates' (likely for templates), there's no indication of context, prerequisites, or exclusions for this list operation.

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