mmex_accounts_delete

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

Without annotations, the description should clearly state behavioral traits. It only states 'Delete' but does not disclose whether the deletion is permanent, if there are prerequisites (e.g., account must have zero balance), or what happens if the account is referenced by transactions. Lacks important behavioral context.

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 concise, starting with the main action, then listing arguments. No unnecessary words. However, it could be more structured with bullet points for better readability.

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?

With an output schema available, the description need not explain return values. However, it omits behavioral details like permanence and prerequisites. The argument descriptions are adequate but not exhaustive.

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 description explains each parameter beyond the schema: id as account ID, db_path as path to .mmb file with env var fallback, db_key as encryption key with env var fallback. Since schema description coverage is 0%, this adds necessary context. However, it doesn't specify constraints like the format of db_path or db_key.

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 ('Delete') and the resource ('account from the MMEX database'). It distinguishes from sibling tools by the resource type. No ambiguity.

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 does not provide any guidance on when to use this tool versus alternatives like mmex_accounts_update or mmex_accounts_get. It lacks usage context, such as recommendations to ensure the account has no dependencies before deleting.

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