how_to_connect

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

No annotations are provided, so the description carries the full burden. It mentions authentication but does not explicitly disclose whether the tool is read-only, whether it triggers any side effects, or what happens when credentials are invalid. The information is not misleading but lacks explicit behavioral clarity.

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, consisting of two sentences that clearly explain the tool's purpose and the models it supports. It avoids unnecessary verbosity while providing relevant context.

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?

The description provides sufficient context for a documentation-oriented tool: it mentions the server, authentication, the range of models, client setup options, and free credits. Since there is no output schema, no return-value details are required.

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 schema has no parameters (0 properties), covering 100% of the schema. The description does not add parameter-specific details because none exist. This matches the baseline for full schema coverage with no param information.

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 tool's purpose: to teach how to connect to the Creative Claw MCP server with authentication. It is distinct from the sibling tools (e.g., get_model_params, list_models) which focus on data retrieval rather than setup guidance.

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 implies usage when needing connection instructions, mentioning setup for multiple clients and free credits. However, it does not explicitly state when to prefer this tool over alternatives or provide a clear 'use this when' condition.

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