mmex_assets_get

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

With no annotations, the description must disclose behavioral traits. It indicates a read operation ('Get') but fails to mention side effects (none expected), error handling (e.g., if ID not found), or authentication requirements (other than env var hints).

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, with a single sentence and a parameter list. It is front-loaded with the action. No wasted words, though structure could be improved with bullet points for 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?

The description adequately covers parameter semantics but lacks usage guidance and behavioral details. Since output schema exists, return values are not needed, but missing context like error behavior or authentication makes it somewhat incomplete for a retrieval tool.

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?

All three parameters are described with their purpose and optionality (env var fallback for db_path and db_key). Schema coverage is 0%, so the description compensates well, though it doesn't specify allowed values or format for id (integer implied).

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 'Get an asset by its ID', specifying the verb and resource. It distinguishes from sibling tools like mmex_assets_list (which retrieves all assets) and mmex_assets_create (which creates).

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 guidance on when to use this tool versus alternatives (e.g., mmex_assets_list for multiple assets). It only explains parameter optionality, missing explicit context for selection.

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