mmex_stocks_list

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

No annotations are present, so the description must cover behavioral traits. It mentions listing stocks but does not disclose that it is read-only, whether permissions are required, or the return format. The db_path/key hints are setup details, not behavioral transparency.

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 very concise: one sentence for the main purpose and a parameter list. It is front-loaded with the core action and contains no extraneous text.

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 output schema exists, the description is adequate for a list operation, but it lacks context about what stocks are (e.g., names, symbols) or any prerequisites. It does not mention that mmex_stocks_get exists for single stocks, which would improve completeness.

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 coverage is 0%; the description adds meaning for both parameters, explaining that db_path is a file path and db_key is for encryption, and that both are optional if corresponding env vars are set. This compensates for the bare schema, though it could be clearer about precedence.

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 'List all stocks in the MMEX database' with a specific verb and resource, clearly differentiating it from sibling tools like mmex_stocks_get (single stock) or mmex_stocks_create.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., mmex_stocks_get for a specific stock). The only usage hints are about optional env vars for db_path and db_key, which do not address tool selection.

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