lanhu_get_designs

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral context beyond annotations: it clarifies that preview_size refers to cover dimensions, not canvas size, and directs that canvas size must be read from Design IR meta.canvas. This helps avoid misuse.

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 concise—two sentences—with no extraneous information. It front-loads the purpose and immediately follows with critical behavioral and workflow details. Every sentence contributes meaningfully.

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 read-only list tool with one parameter and no output schema, the description provides adequate context: purpose, output fields, a behavioral caveat, and follow-up use. It is complete enough for an agent to use correctly in the workflow, though it does not mention potential pagination or other limits.

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% as the single parameter 'url' has a description. The tool description does not add new information about the parameter beyond what the schema provides, so it meets the baseline without adding extra semantic value.

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 it retrieves a list of UI designs from a Lanhu project, specifying the fields (index, id, name, cover URL, cover size). It distinguishes itself from sibling tools by explicitly positioning itself as the first step and directing subsequent calls to lanhu_get_design_schema or lanhu_get_design_slices using the returned index or id.

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 explicitly marks itself as '[第一步]' (step 1) and instructs the user to use the returned values to call other tools. This provides clear usage context and workflow guidance, though it does not explicitly state when not to use this tool.

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