LibreLink MCP Server

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

The description adds valuable context beyond the 'destructiveHint: true' annotation by specifying that it clears 'stored tokens' and forces 're-authentication', clarifying the behavioral impact. It doesn't contradict annotations and provides useful operational details, though it could mention potential side effects like requiring re-login.

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 front-loaded with the core action and resource, followed by a clear usage guideline in a second sentence. Both sentences earn their place by providing essential information without redundancy or unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, destructive operation) and lack of output schema, the description is largely complete. It explains what the tool does and when to use it, though it could briefly note the absence of parameters or expected outcomes after clearing.

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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description appropriately doesn't discuss parameters, as none exist, and focuses on the tool's purpose and usage instead, which is efficient and contextually relevant.

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 specific action ('Clear') and resource ('authentication session and stored tokens'), distinguishing it from sibling tools like 'get_session_status' or 'configure_credentials'. It precisely defines what the tool does without being vague or tautological.

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 explicitly provides when to use this tool ('if you need to force a re-authentication'), offering clear guidance on its purpose. It differentiates from alternatives by focusing on session clearing rather than configuration or retrieval operations present in sibling tools.

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