telepath_setup_help

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It communicates that the tool surfaces setup instructions, but it doesn't explicitly state that the tool performs no configuration itself or describe the output format. The instructional tone implies it's informational, but this could be more explicit.

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 concise and well-structured, using a warning icon, bulleted list of environment variables, and numbered configuration steps. Every element serves a purpose, and the most critical information (missing configuration) is front-loaded.

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 setup-help tool with no parameters, no output schema, and no annotations, the description fully covers the necessary context: the problem, the specific environment variables needed, and two ways to set them. It is self-contained and complete for its intended use.

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 is empty. According to the rubric, 0 params earns a baseline score of 4. The description adds no parameter details simply because there are none to explain.

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 explicitly states the tool's purpose: addressing TelePath not being configured and instructing the user to set environment variables. It names the specific resources (TELEPATH_USERNAME, TELEPATH_PASSWORD) and provides actionable steps, making the intent unambiguous even without sibling 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?

The description clearly defines the context in which this tool is relevant: when TelePath is unconfigured. It lists two concrete configuration methods, giving the agent and user clear usage guidance. While it doesn't mention alternatives or exclusions, the absence of siblings makes this acceptable.

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