list_asset_layouts

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

With no annotations, the description must disclose behavior but only implies a read-only operation via 'Get'. It does not mention pagination behavior despite a 'page' parameter, default filtering, or whether the result is comprehensive across all asset layouts.

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 a single short sentence with no wasted words, which is appropriately concise for a simple listing operation. However, it is under-specified, lacking any parameter or context details, so it falls short of a higher score.

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 is wholly insufficient for a tool with five optional parameters and no output schema or annotations. It fails to clarify what an Asset Layout is, how parameters interact, how pagination works, or what the response contains, leaving major knowledge gaps.

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 schema has five parameters with zero description coverage, and the tool description does not explain any of them. Parameter names like 'slug', 'active', and 'updated_at' lack context, so the agent cannot infer their purpose or expected formats from the description.

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 'Get a list of Asset Layouts' uses a clear verb ('Get') and specific resource ('Asset Layouts'), distinguishing it from the singular get_asset_layout and other asset layout operations. It is slightly minimal but unambiguous about the core action.

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 like get_asset_layout, or when filtering by parameters like active or updated_at would be relevant. There is no mention of exclusions or preferred contexts.

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