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

The description frames this purely as a safe read ("Read authorized Film sections"), while annotations declare readOnlyHint=false and destructiveHint=true with openWorldHint=true. Nothing in the text explains what mutation or destructive effect is possible, what would be destroyed, or how the open-world behavior manifests; the closing sentence about "saved mutation receipts already verify successful edits" is opaque jargon rather than disclosure.

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?

Three short sentences with the purpose front-loaded, which is good structure. The final sentence ("The supplied authoring revision and saved mutation receipts already verify successful edits") is unexplained and does not clearly earn its place, and the middle sentence compresses two distinct modes into one clause.

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?

This is a complex, 6-parameter tool with nested arguments, required bootstrap artifacts (read_skills, expected_catalog_version, request_key), a ten-value section enum, and pagination via cursor — none of which the description explains beyond the view/source_path hints. An output schema exists so return values need not be described, but the invocation prerequisites and the destructive contradiction remain unaddressed.

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?

At 50% schema coverage, the description does add meaning for two parameters: the default behavior of view and how source_path is meant to be expanded (with schema giving the path syntax). It says nothing about section, purpose, cursor continuation, work_id, read_skills, request_key, expected_catalog_version, or expected_revision, so half the surface is left to the schema alone.

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 gives a specific verb+resource ("Read authorized Film sections") and hints at the payload shape (current state vs history/edit indexes). It does not differentiate from the many sibling read tools such as native.read_film_studio_production_review, native.read_film_studio_action_contract, or native.list_film_studio_project_work, so an agent cannot tell from the text alone why it would pick this reader over those.

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?

It offers in-tool guidance on how to use the views (default current/index, "Expand an exact source_path for details", "view=full for a complete review"), which is genuinely useful routing between modes. It gives no guidance on when to use this tool at all versus sibling read/list tools, and no prerequisites or exclusions are stated.

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