lightroom_get_develop_preset

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

With no annotations provided, the description carries the burden of disclosing behavior. 'Inspect' effectively communicates a read-only, non-destructive operation, and 'internal adjustment parameters' tells the agent exactly what data is exposed. It does not discuss error conditions or edge cases, but for a simple inspection tool this is adequate.

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, focused sentence with no filler. It front-loads the action and resource immediately, making it easy to parse and act on.

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?

The tool is simple and an output schema exists, so return-value documentation is not needed. However, the description lacks usage guidance and parameter semantics, leaving the agent to infer important operational details about how to correctly invoke the tool.

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%, and the description does not explain the preset_name parameter at all. An agent can infer from the tool title that preset_name identifies a Develop preset, but the description adds no detail about whether an exact name is required, how names are matched, or what happens when the preset does not exist.

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 uses a specific verb, 'Inspect', tied to a concrete resource: 'internal adjustment parameters stored inside a Develop preset.' This clearly distinguishes the tool from sibling operations like apply, create, export, or compare, and makes the tool's unique role evident.

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 context is implied: an agent would use this when needing to see the internal parameters of a Develop preset. However, the description provides no explicit guidance about when not to use it or which alternative sibling tool might be more appropriate, such as list_develop_presets or compare_develop_presets.

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