list_mobile_layouts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, which convey safety and idempotency. The description adds no additional behavioral traits beyond the annotations. Thus, the description does not add value beyond what is already structured, but also does not contradict annotations.

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 extremely short (one sentence) but lacks essential details about the parameter or the nature of the results. Under-specification is not conciseness; the description fails to make every sentence earn its place because it omits critical information.

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 tool's simplicity (1 optional parameter, no output schema), the description should at least hint at what a mobile layout configuration is or what the list returns. It provides no context about the resource or output structure, leaving the agent underinformed.

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 0%, meaning the schema provides no description for the 'limit' parameter. The tool description does not mention the parameter at all, failing to explain its purpose (e.g., controlling the number of results). With the full burden on the description, this is a severe gap.

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 ('mobile layout configurations'), providing a specific verb+noun. However, it does not differentiate from sibling tools like list_mobile_app_configs or list_mobile_applets, which could cause confusion. A score of 4 reflects clarity but missed opportunity for distinction.

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 given on when to use this tool versus alternatives (e.g., list_mobile_app_configs). The description lacks context about prerequisites, filtering, or comparison with similar tools. This provides no help for the agent to decide when to invoke this tool.

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