mdb_parameters

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'List parameters,' implying a read-only operation, but does not disclose other behavioral traits like authentication needs, performance, or potential limitations. More detail is needed for a non-annotated tool.

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 short sentence, which is concise but too minimal. It lacks important details that could be included without verbosity, such as filtering capabilities or relationship to sibling tools. The brevity sacrifices informativeness.

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 of the tool (3 optional parameters, many siblings) and the presence of an output schema, the description is incomplete. It fails to contextualize the tool's role within the MDB suite or explain when this list is appropriate versus other parameter-related tools.

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?

Schema description coverage is 100%, so the input schema already describes all parameters adequately. The tool description adds no extra meaning beyond the schema, meeting the baseline for high coverage. No improvement or detraction.

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' and the resource 'parameters from the Mission Database,' which distinguishes it from sibling tools like mdb_commands or mdb_get_parameter. However, it lacks explicit differentiation details, such as scope or filtering capabilities, that are present in high-scoring examples.

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. It does not mention prerequisites, exclusions, or context for use. With many sibling MDB tools, the agent would benefit from explicit usage instructions, which are absent.

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