pcb_get_silkscreens

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'query all silkscreen text'. It does not describe what data is returned, whether coordinates or text strings are included, or whether an open board context is required.

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 short sentence with no filler, stating the action and the target resource directly. It is appropriately sized for a simple parameterless query tool.

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?

The description is minimally sufficient for a zero-parameter read tool, but it lacks detail about the expected return contents and any operational context such as requiring an open PCB document. Since there is no output schema, a bit more description would make the tool easier to use correctly.

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 input schema has zero parameters, so there are no parameter semantics that the description needs to clarify. The baseline for a zero-parameter tool is 4, and no additional parameter-specific information is required.

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 states a clear action, '查询' (query), and a clear resource, '所有丝印文字' (all silkscreen text). It is understandable on its own, though it does not explicitly differentiate it from sibling silkscreen-related tools such as pcb_move_silkscreen or pcb_auto_silkscreen.

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 guidance about when to use this tool versus related tools, nor any mention of prerequisites such as an open PCB document. An agent must infer usage entirely from the tool name and the brief description.

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