Request a local write key from Zotero

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

The description discloses the interactive behavior: Zotero shows a confirmation dialog, the user must approve it, and the returned key must be stored in an environment variable. It also covers failure behavior. This goes well beyond the basic readOnlyHint/idempotentHint/destructiveHint annotations.

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 compact and well-structured: it states the action first, then the user steps, the access distinction, and the return value. Every sentence contributes useful information without repetition or filler.

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 no-parameter authorization tool, this description is complete. It explains the prerequisite user interaction, the environment variable to set, the restart requirement, the read/write distinction, and the possible return outcome, so an agent can guide the user through the full flow.

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, so the baseline is 4. The description adds meaningful context about the returned key and the post-approval workflow, even though there are no input parameters to document.

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 opens with a specific verb and resource: 'Ask the Zotero desktop application for a local API key.' It clearly identifies the tool as the authorization step for local write access, which distinguishes it from the many sibling data-read and data-write tools.

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 explicitly states when this tool is needed: 'writes over the local transport do,' and when it is not: 'Read access does not need this.' It also gives follow-up steps (copy the key and restart the MCP client), so an agent knows exactly how to use the result.

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