rate_photos

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals only the runtime prerequisite and does not state whether an existing rating is overwritten, whether the operation is reversible, what happens if darktable is not running, or error behavior. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

Two sentences with zero waste. The action is front-loaded, and the prerequisite sentence earns its place by warning the agent about a hard runtime requirement. Nothing redundant or extraneous.

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?

For a simple 2-parameter tool with fully documented schema, the description covers the core action and the critical prerequisite. However, it lacks differentiation from the near-duplicate sibling 'apply_ratings_batch', and with no annotations or output schema, a bit more behavioral context would make it fully self-sufficient.

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 100%, with both 'photo_ids' and 'rating' fully documented in the input schema (including the rating scale -1/0/1-5). The description adds no meaningful parameter meaning beyond the schema, so the baseline of 3 applies.

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: 'Apply a star rating to one or more photos in the user's darktable library.' This is clear and unambiguous. However, it does not distinguish itself from the sibling tool 'apply_ratings_batch', which appears to perform a nearly identical operation, so it misses the sibling-differentiation mark for a 5.

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 provides a runtime prerequisite (darktable running with the darktable-mcp Lua plugin installed) but gives no guidance on when to use this tool versus alternatives like 'apply_ratings_batch'. There is no mention of exclusions, precedence, or which tool fits a given scenario, so an agent gets no tool-selection help.

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