get_graphics_white_luminance

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

No annotations are provided, so the description carries the full behavioral burden. It only states that the tool 'gets' a value, without disclosing return format, units, possible side effects, or what 'white luminance' refers to in Premiere Pro. Minimal inferable read-only behavior, but not enough transparency.

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 short, but its only substantive content largely repeats the tool name. The phrase 'Premiere Pro expanded operation' is filler that does not earn its place and provides no useful structure.

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 no output schema and no annotations, an agent still does not know what the tool returns, how the returned white luminance is represented, or what scenarios require this operation. The description is barely adequate for correct 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 tool has zero parameters and schema description coverage is 100%, so the absence of parameter explanations is not a meaningful gap. The baseline for 0 parameters is 4.

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 states a specific verb and resource: 'get graphics white luminance.' This makes the purpose reasonably clear and distinguishes it from the sibling set_graphics_white_luminance. However, it adds no detail about what 'white luminance' means or how it differs from other getters, so it is not a top-tier purpose description.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention the setter counterpart or any related get, nor does it describe the context in which this operation would be appropriate.

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