list_asset_slots

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

With no annotations, the description carries the burden of behavioral disclosure. It explains what the tool returns (slots and their current asset assignments), and that slotKeys can be discovered from it. While it doesn't explicitly state read-only behavior, the verb 'List' and the framing strongly imply a safe, non-mutating operation.

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?

Two concise, front-loaded sentences with no waste. The first sentence states the core functionality and output, the second adds the key usage guidance and side-page variant.

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 list tool with a complete schema, the description covers the main purpose, output content, and how to inspect side pages. It lacks explicit auth/error behavior, but that is not critical for this straightforward read operation. The absence of an output schema is mitigated by describing what the response includes.

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 coverage is 100%, providing detailed parameter descriptions. The description adds useful context beyond the schema by explaining the purpose of the returned slotKeys and reinforcing the role of sidePageSlug. This elevates it slightly above the baseline.

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 identifies the tool as listing asset slots (placeholders) for landing or side pages, including current asset assignments. It differentiates from the closely related assign_asset_to_slot by explaining this is the discovery step, and from list_assets by focusing on slots rather than assets.

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?

Explicitly states when to use this tool: 'Use this to discover valid slotKeys before calling assign_asset_to_slot.' It also clarifies the side-page alternative with 'Pass sidePageSlug to inspect a side page's slots.' It doesn't list exclusions or contrast with list_assets, but the primary use case is clear.

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