place_image

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The description only mentions 'advanced options' without detailing any behavioral traits, such as whether the tool modifies an existing document, requires a document to be open, or has side effects like creating frames. The lack of behavioral context is a significant gap.

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 very concise (one short sentence), but it lacks substance. While it front-loads the action, the phrase 'with advanced options' is too vague to be informative. Every sentence does not earn its place; the description could be improved with more specific details.

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 tool has 8 parameters (1 required) and no output schema, the description is insufficient. It does not cover return values, prerequisites (e.g., open document), or the effect on the document state. The high parameter count demands more context than provided.

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 description coverage is high (88%), with parameters like x, y, width, height, fitOption, and createFrame already documented in the schema. The description adds minimal value beyond the schema, only stating 'advanced options' without clarifying which options are available or how they affect placement. Baseline of 3 is appropriate.

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 verb 'Place' and the resource 'image', indicating the tool's primary action. However, it lacks differentiation from sibling tools like create_rectangle or create_text_frame, which also involve placement but of different objects. The phrase 'with advanced options' hints at additional capabilities but is vague.

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 provides no guidance on when to use this tool instead of alternatives. Given the large set of sibling tools (e.g., create_ellipse, create_text_frame), the description should clarify the context, such as when placing an image is preferred over other creation tools. No when/why context is provided.

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