context_guide

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

With no annotations, the description at least implicitly acknowledges it's a read-only introductory aid, but does not detail output format or what happens if called repeatedly. Some prior exposure to the tool family or server is needed to appreciate its purpose.

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 short and direct, delivering both purpose and when-to-use in two sentences, front-loading the core message without extra bulk.

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 zero-parameter tool, the description covers purpose and usage. It doesn't mention any potential side effects or the exact content, but given the simplicity, it is largely complete.

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, and the schema provides high coverage (100%), so the baseline is high. The description appropriately focuses on the tool's behavior rather than parameter details, which are irrelevant here.

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?

Description clearly states the tool explains how to use the server and the intended workflow, combining guidance with a recommendation to call it once for new users. It distinguishes itself from siblings by being meta-guidance about the tool family, not a specific operation.

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 tool explicitly tells the agent when to call it ('if you have not used these tools before') and its purpose in onboarding. It distinguishes from siblings because they perform specific operations, while this provides overarching usage guidance.

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