Catalog MONA Agent

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description is consistent with those, adding that templates can be read from local storage, a catalog URL, or an integrated wave 1 catalog. It does not add much beyond the annotations and does not describe return format or source-selection behavior.

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 core purpose is front-loaded in the first sentence, but the second sentence is an unrelated deployment workflow that does not help an agent call agent_templates_list correctly. It is short, but not every sentence earns its place.

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 no-parameter, read-only tool with annotations covering safety and no output schema, the description is minimally adequate. However, mixing in deployment steps makes the tool's role relative to agent_templates_get, agent_deploy, and cloud_app_create less clear, leaving ambiguity about when this catalog list is the right choice.

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 tool has zero parameters, so the baseline for parameter semantics is 4. The description mentions three template sources but does not document any input fields, which is acceptable because the schema contains no parameters to explain.

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 first sentence states a specific verb and resource: 'Đọc template' from local directory, catalog URL, or integrated wave 1 catalog. However, it does not distinguish this tool from the sibling agent_templates_get, and the second sentence about deploying a project via cloud_app_detect and cloud_app_create muddles what agent_templates_list itself does.

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 names source locations but does not say when to choose this tool over agent_templates_get or other siblings. The only workflow guidance is for deployment ('Deploy dự án: cloud_app_detect rồi cloud_app_create'), which is a different task rather than instruction on using this listing tool.

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