create_mobile_layout

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

The description's '[Write]' tag merely restates what is already implied by readOnlyHint=false and does not add meaningful behavioral context. No information is given about side effects, permission requirements, or handling of existing layouts, though annotations already cover the basic write safety profile.

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 one short sentence plus a tag, with no filler. It is minimally sized but not excessively verbose; however, it is arguably too terse to provide substantial value.

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 no output schema and a very sparse description, the agent lacks information about return values, error conditions, or how 'view' corresponds to parameters. The openWorldHint=true suggests unknown behaviors that are not explained, leaving the description incomplete for a create 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?

The input schema covers all three parameters with descriptions (100% coverage). The tool description adds no additional parameter semantics beyond what the schema provides, and the phrase 'specific view' does not clearly map to the 'table' or 'type' parameters.

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 uses a specific verb ('create') and resource ('mobile layout') with context ('for a specific view'), clearly distinguishing it from list_mobile_layouts and other creation tools like create_mobile_applet. However, 'specific view' is ambiguous and not defined in the description, preventing a perfect score.

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 such as create_mobile_applet or list_mobile_layouts. There is no mention of prerequisites, intended scenarios, or exclusions.

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