place_file_on_page

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

No annotations are provided, so the description bears the full burden. It fails to disclose critical behavioral traits: whether the file is imported, linked, or embedded; what file types are supported; side effects like overwriting or placing; or any dialog interactions (despite a 'showingOptions' parameter).

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 sentence, which is concise but under-specified for a 7-parameter tool. It front-loads purpose but fails to earn its place by omitting essential context and structure.

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's complexity (7 parameters, 2 required, no output schema), the description is severely incomplete. It does not explain what 'placing' entails, the result of the operation, or how parameters interact. No output schema exists to compensate.

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% with basic descriptions for each parameter (e.g., 'Page index', 'Path to file to place'). The tool description adds no further parameter context, but the schema itself provides minimal meaning. Baseline score of 3 is appropriate as the schema carries the weight.

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 'Place a file on a page' clearly states the action and target (file + page), distinguishing it from spread-level alternatives like 'place_file_on_spread'. However, it lacks specificity on file types, which could be inferred from sibling 'place_image' or 'place_xml_on_page'.

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?

No guidance is provided on when to use this tool versus sibling tools like 'place_image' or 'place_xml_on_page'. There are no usage cases, prerequisites, or exclusion criteria mentioned.

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