ps_create_text_layer

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

Apart from idempotentHint=false, annotations provide minimal behavioral disclosure. The description adds valuable context that the text is editable (vector), which helps the agent understand the result beyond just a static layer. It does not contradict any annotations.

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 concise at two sentences, front-loaded with the primary purpose and followed by a relevant usage tip. Every sentence adds value and there is no redundancy.

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?

Given the 4-parameter schema with full description coverage and an output schema, the description sufficiently explains the tool's core behavior and next steps. No critical information is missing for an agent to invoke it 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?

Schema coverage is 100% and the description's mention of content, position, and font size mirrors the schema parameters without adding extra semantics like units or formatting rules. It is acceptable but does not enhance beyond the schema.

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 the action 'Create a new text layer' and specifies what the tool does with content, position, and font size. It distinguishes itself from generic layer tools like ps_create_layer by specifying 'text' and noting the vector/editable nature.

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 gives a clear follow-up instruction: 'Use ps_set_text (property=font / color) afterwards to style.' This indicates when to use the tool (initial text creation) and what to do next, though it does not explicitly mention exclusions or alternatives beyond ps_set_text.

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