Validate Ossie model

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description needn't restate safety, but it adds real context: the bundled schema version, automatic 0.1.1→0.2.0 conversion, and the explicit note that execution is local with nothing sent to Tableau. The enumerated semantic checks further disclose what failure modes to expect. It stops short of describing error/report shape, but an output schema exists for that.

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?

Front-loaded with verb and resource, then the validation targets, then the conversion caveat, then the locality note — a sensible ordering with little waste. The mid-sentence list of semantic rules is dense but each item is informative rather than padding.

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?

With an output schema present, return values needn't be explained, and both parameters plus the version-conversion edge case are covered. For a two-parameter read-only validator, an agent has everything needed to call it correctly.

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%, so the description carries the burden and largely does: `document` is identified as YAML or JSON text, and `model_name` is explained as the disambiguator for 0.1.1 documents holding several models. It doesn't clarify `model_name` behavior for 0.2.0 documents or what happens when it's omitted/ambiguous, which is the remaining gap.

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?

States a specific verb (validate) and resource (Apache Ossie model given as YAML/JSON text), plus the exact standard it checks against (bundled JSON Schema 0.2.0.dev0 and spec semantic rules). This is clearly distinguishable from the sibling import/export tools, which move data rather than check it.

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?

Usage is implied rather than stated: the agent can infer this is a pre-flight check for Ossie documents, and the description gives a conditional rule for `model_name` on multi-model 0.1.1 documents. However, it never names an alternative or says when not to use it (e.g., versus import_from_ossie, which presumably also parses documents), leaving routing to inference.

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