zepp_raw_request

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

With no annotations, the description carries full behavioral transparency burden. It discloses the HTTP method (GET) and scope ('arbitrary'), but does not reveal authentication requirements, error handling, rate limits, or how the response is returned. This is a significant gap for a tool that sends requests to a third-party API.

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 extremely concise, consisting of two sentences that are front-loaded and directly informative. No filler or redundant details.

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 simple structure and presence of an output schema, the description covers purpose and usage context well. However, the lack of parameter semantics and behavioral caveats (authentication, error handling) makes it incomplete for an agent to invoke correctly without guessing.

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?

Schema description coverage is 0%, and the description does not explain the meaning of 'path' and 'params' beyond their names. It fails to specify that 'params' are query parameters or how the URL is constructed, requiring the agent to infer behavior from context.

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 action ('Send an arbitrary GET to the Zepp API'), specifies the HTTP method, and gives a distinct purpose ('endpoints this server does not model yet'). This differentiates it from sibling tools that target specific Zepp APIs.

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?

It explicitly says when to use this tool: 'Use this to reach endpoints this server does not model yet.' This implies using dedicated tools for modeled endpoints, though it doesn't list specific exclusions or alternatives.

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