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

With no annotations, the description carries the full burden of explaining side effects, access requirements, or limitations. It mentions 'Task text discarded' and 'no disk access' for individual parameters, but does not clarify overall behavior, network usage, costs, or whether external services are contacted.

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 brief and not overly verbose, but the brevity comes at the cost of clarity. Key information about the tool's operation and output is missing, so the conciseness is not effective.

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?

There is no output schema, no example response, no error behavior, and no explanation of how the nine optional parameters relate to the stated purpose. An agent would not know what to pass or what to expect back.

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?

While every parameter has a schema description, most are cryptic or self-referential, e.g., 'Git ref name; discarded after the shape check' and 'Search text; discarded after the length check'. The descriptions do not explain how these parameters are used or what values are acceptable beyond basic types.

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 states it finds a 'public pay-per-call tool gateway' for tasks like weather, search, scrape, or voice, but does not clearly define what a tool gateway is or how it relates to the listed parameters. It is not well distinguished from sibling tools such as weather-hint, web-fetch, or search-query-len.

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?

No guidance is provided about when to use this tool versus the many sibling tools. The examples of weather, search, scrape, or voice are too broad and do not explain selection criteria or expected inputs.

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