list_encoders

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

With no annotations provided, the description carries the full burden. It discloses the output format (table of names, ranks, descriptions) but does not mention potential side effects, permissions, or any operational caveats. For a read-only listing tool this is adequate but not exhaustive.

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 three sentences with no wasted words. It front-loads the primary purpose, explains the use case, and ends with the output format. It is concise and well-structured, though it could be slightly more explicit about default behavior (no filters) for absolute clarity.

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 simple listing tool with two optional filters and no output schema, the description covers the essential elements: what it lists, why to use it, how to filter, and what the output looks like. It is complete enough for an agent to call correctly, though it omits details about rank definitions or the full list of platforms/architectures supported beyond the given examples.

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 description coverage is 100%, so both arch and platform are already documented. The description reinforces filtering by these fields but adds no new semantic detail beyond what the schema provides. Baseline 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 clearly states the verb 'List' and the resource 'all available msfvenom encoders' with their ranks and descriptions. It distinguishes itself from related sibling tools like list_payloads by specifying 'encoders', though it does not explicitly name any alternative.

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?

It provides a clear use case: 'Use to find the best encoder for your target architecture' and explains how to filter by platform or architecture. It does not mention when not to use this tool or alternatives, but the guidance is sufficiently clear for selection.

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