Run Advanced Layout Analysis

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

The description only states the operation name without disclosing side effects, costs, or asynchronous nature. The annotations indicate it is not read-only, but the description does not add behavioral context beyond what annotations provide.

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 of 7 words, efficiently conveying the tool's core purpose with no extraneous information.

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 11 parameters and no output schema, the description lacks information about the output format, job behavior, and implications of the parameters, leaving the agent with insufficient context for reliable invocation.

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?

The input schema covers all 11 parameters with descriptions (100% coverage), so the description does not need to elaborate further. It merely says 'additional parameters' which is consistent with the schema.

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 'Run' and resource 'advanced layout analysis', and the term 'advanced' distinguishes it from the sibling tool 'transkribus_la_analyze'.

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 implies through 'advanced' and 'additional parameters' that this tool is for more complex scenarios, but it does not explicitly state when to use this tool versus the basic 'transkribus_la_analyze' or other siblings.

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