Mencoro setup instructions

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds valuable context beyond the annotations by explaining the current missing-token state and why data reads fail until setup finishes. This aligns with and reinforces the annotation hints without contradicting them.

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 two sentences with no filler. The primary purpose is front-loaded in the first sentence, and the second sentence provides essential context. Every word earns its place.

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 explanatory tool with no parameters and no output schema, the description covers the necessary context: what the tool does, the current state, and the consequence of inaction. The output is implicitly instructions, which is clear from the verb 'Explain'. It could detail the output format, but this is not critical given the tool's simplicity.

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 input schema has zero parameters, so there is nothing for the description to clarify. Per the baseline for zero-parameter tools, the description adequately handles parameter semantics by not adding unnecessary detail.

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 ('Explain') and names the exact resource ('finish connecting this bridge to Mencoro'). It also states the practical consequence of missing configuration, leaving no ambiguity about what the tool does. With no sibling tools, there is no differentiation burden.

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 clearly implies the context of use: the bridge has no API token, so data cannot be read until setup is complete. This tells an agent when to invoke the tool (when configuration is needed or when Mencoro data is unavailable). It does not explicitly mention alternatives, but none exist.

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