dts_publish_osgb

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

With no annotations, the description carries the burden. It discloses that the tool runs two sequential stages and that 'ok' is true only if both succeed, which is useful. However, it omits other behavioral aspects such as side effects, overwrite behavior, or error handling, leaving gaps for an agent.

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 concise, with two short paragraphs that front-load the purpose and then add essential context. Every sentence is informative and no words are wasted.

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 no annotations, the description is incomplete. It explains the overall process but omits crucial details about parameter usage, return format, and how optional settings affect behavior, making it inadequate for full autonomous 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?

Schema description coverage is 0%, but the description does not mention any of the five parameters (inpath, outpath, flags, timeout, async_pyramid) or their meaning. It adds no value beyond what the bare schema shows, failing to compensate for the lack of parameter descriptions.

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 tool publishes oblique-photogrammetry OSGB data with a specific verb and resource. It also explains the two-stage process, distinguishing it from the sibling dts_publish tool which likely handles other data types.

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 usage for OSGB publishing and provides context that both tiling and LOD pyramid stages are required. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to understand when this tool is appropriate.

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