jlcpcb_pcb_stencil_price_config

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add useful context by stating 'Requires API credentials' and 'Official PCB API', but it does not explicitly state that this is a read-only operation, nor does it describe the response format or any rate limits. The 'get' verb implies reading, but the description could be more transparent about expected behavior.

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, front-loaded sentence that immediately conveys the tool's purpose and then adds the essential credential requirement. There is no redundant or filler content; every word earns its place.

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-parameter, simple getter tool with no output schema, the description is nearly complete. It states what it does and the auth prerequisite. However, it lacks any note about return value characteristics or potential error scenarios, which could be valuable for an agent deciding whether to invoke it. Still, it is adequate for the simplicity of the tool.

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, so the schema is trivially complete (100% coverage). The description does not need to explain parameter semantics because there are none. This aligns with the baseline for 0-parameter tools, where the description's clarity about the operation is sufficient.

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 a specific verb ('get') and a specific resource ('SMT stencil (steel) price configuration'), which distinguishes it from sibling tools like jlcpcb_pcb_calculate_price that handle full PCB pricing. The mention of 'Official PCB API' further clarifies its provenance.

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 explicit guidance on when to use this tool versus alternatives. While the resource is specific, the description does not mention exclusions or alternatives, such as using jlcpcb_pcb_calculate_price for general PCB pricing. The only prerequisite mentioned is API credentials, but that is a general requirement rather than a usage guideline.

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