verify_premiere_connection

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

The description claims the tool is 'safe, read-only' and provides behavioral details about not returning project names, paths, or media details. However, the annotations include readOnlyHint=false, which directly contradicts the 'read-only' claim. Per rubric, a contradiction with annotations yields a score of 1. The additional transparency about privacy is negated by this inconsistency.

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, well-structured sentence that immediately states the tool's safety and purpose. It is concise, front-loaded, and contains no fluff or repetition of schema details.

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 connectivity check with only one optional parameter and no output schema, the description provides enough context for an agent to understand what the tool does and what it guarantees. The contradiction with annotations slightly undermines completeness, but the core functionality and constraints are well communicated.

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%, as the single parameter 'backend' is fully described in the schema with an enum and explanation. The tool description adds no new parameter semantics, which is acceptable given the schema already covers it, 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 clearly states the tool's purpose: 'Run a safe, read-only first-run check... proves that this MCP server, the selected Premiere bridge, an active project, and an active sequence are connected.' It uses a specific verb ('verify' implied) and resource (connection), and distinguishes itself from sibling tools by focusing on connection verification rather than retrieving data.

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 gives clear context: this is a first-run check, suggesting it should be used at startup or when verifying the environment. It implies its safe, read-only nature makes it appropriate for initial diagnostics. However, it does not explicitly name alternative tools or state when not to use it, though this is not critical for a connectivity check.

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