place_xml_on_spread

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

No annotations are provided, and the description does not disclose behavioral traits. It does not indicate whether placing XML creates new objects, overrides existing content, or requires a predefined XML structure. The agent cannot infer side effects or prerequisites.

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 at one short sentence, but it sacrifices necessary context. It is not verbose, but it is too sparse to be fully effective. Every word earns its place, but more information is needed.

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 5 parameters, no output schema, and siblings that perform similar actions, the description is incomplete. It lacks explanation of the operation's effect, required document state, and return behavior. A more complete description would improve agent reasoning.

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?

Input schema covers 100% of parameters with descriptions, so the description adds no extra meaning. Baseline score of 3 is appropriate as the schema does the work, but the description does not enhance parameter understanding (e.g., units for x/y, effect of autoflowing).

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 states 'Place XML content on a spread,' which is a clear verb+resource, but it does not differentiate from siblings like place_xml_on_page or place_file_on_spread. The term 'place' is ambiguous—does it create text frames or import data? The purpose is minimally clear but lacks specificity.

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 on when to use this tool versus alternatives. With siblings like place_xml_on_page and place_file_on_spread, the description should explain context (e.g., when to place on spread vs page). No usage or exclusion information provided.

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