place_xml_on_page

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

No annotations are provided, so the description must carry the full burden. It merely states 'Place XML content' without disclosing whether it creates a new page item, what happens if the xmlElementName doesn't exist, or the effect of the 'autoflowing' 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?

At only 5 words, the description is concise but may be too minimal for a tool with 5 parameters. It frontloads the core action but omits important context, making it average in 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 absence of an output schema and annotations, the description lacks completeness. It does not explain the source of XML content, the visual result, or the impact of 'autoflowing', leaving the agent underinformed.

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?

All 5 parameters are described in the schema with 100% coverage. The description adds no additional meaning beyond what the schema already provides, earning a baseline score.

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?

Description clearly states the action ('Place XML content') and resource ('a page'), differentiating from sibling 'place_xml_on_spread'. However, it doesn't specify that 'XML content' refers to an XML element from the document's XML structure, which is implied by the parameter name 'xmlElementName'.

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 alternatives like 'place_file_on_page' or 'place_image'. The description lacks context about prerequisites, such as the need for an existing XML structure in the document.

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