list_topstitch_styles

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

No annotations are provided, so the description carries the behavioral transparency burden. It communicates a read-only listing action and project scope, but it does not disclose output format, ordering, or whether the returned values are names, ids, or objects. Basic behavior is clear, but the full return contract is unspecified.

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?

A single sentence that front-loads the primary action and resource, then immediately adds the key consumer context. There is no filler or repeated schema information.

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 zero-parameter list tool, the description is complete: it states what is listed, in what scope, and why the result matters. The reference to add_topstitch's style_index is enough for an agent to know both when to call it and how to use its result.

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 has zero parameters show dash the input schema is fully covered at 100%, and the baseline for no-parameter tools is 4. There is no parameter-level detail needed beyond what the empty schema already makes obvious.

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 names a specific verb ('List'), a clear resource ('topstitch styles'), scopes it to 'the project', and gives an explicit purpose ('for add_topstitch's style_index'). This also distinguishes it from siblings like get_topstitch_style, which implies singular retrieval, and create/set/add mutations.

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 'for add_topstitch's style_index' clause provides a clear when-to-use context: call this before add_topstitch to obtain a valid style_index. It does not explicitly mention alternatives or exclusions, but for a zero-parameter list tool this is clear enough.

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