Add Text

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

Disclosure that the text layer becomes active adds behavioral context beyond annotations (which are non-contradictory). No details on error handling or permission needs, but adequate for a creation tool.

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?

Two sentences with no redundancy. First sentence covers purpose and side effect; second sentence adds key parameter guidance and references to sibling tools.

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?

Completeness is high given no output schema: covers side effects, parameter behavior, and tool interdependencies. Missing mention of return value or error cases, but acceptable for a straightforward creation 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?

Adds meaning beyond schema by explaining paragraphBounds distinction and font discovery workflow. Schema coverage is 100%, so description enhances rather than compensates.

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: 'Add a new text layer to the active document at the specified position.' It distinguishes from siblings like edit_text and adds behavioral context (layer becomes active).

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?

Provides explicit guidance on using paragraphBounds for word wrapping vs point text, and references load_font/list_fonts for font setup. Could be more explicit about when to avoid this tool, but the context is sufficient.

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