list_starters

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

No annotations exist, so the description carries the full burden. It does disclose the shape of the return data (the five starter types, the six style values, and that each style reports whether it uses a shared header/footer), which is useful, but it says nothing about ordering, size, or that the operation is a read-only enumeration.

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?

It is short with no padding, but it is a single sentence fragment that begins mid-thought ('Starting points: …') rather than front-loading what the tool does. The list of styles in parentheses is dense and could be one clause instead.

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 no-param listing tool with no output schema, the description does describe the returned content, which is the most important thing. However, it omits the natural next step (feeding a starter into create_from_starter or preview_starter) and any note on ordering or uniqueness, leaving the workflow incomplete.

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 tool takes zero parameters, which is the baseline-4 case. The description introduces no parameter concepts that would be needed, and the empty schema is consistent with a parameterless enumeration.

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 enumerates what the tool returns (blank, quotation, invoice, purchase, product start points with their styles), which implies a listing operation, but it never states a verb or says it lists available starters. The name 'list_starters' supplies the action, so the description mostly restates the resource rather than adding clarity.

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?

There is no indication of when to call this versus the many sibling listing tools (list_templates, list_parts, list_models) or how it pairs with create_from_starter/preview_starter. The agent must infer that this is the discovery step before creating a document from a starter.

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