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

With no annotations, the description must fully disclose side effects, cost, persistence, and output behavior. It only vaguely mentions 'pay-per-call' and 'Returns connection methods' without explaining implications. Phrases like 'discarded after the check' hint at non-persistence but are not explicit enough to count as transparent.

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 not overly verbose, but it includes confusing, seemingly contradictory statements like 'Task text discarded' and param descriptions that add noise rather than clarity. A concise description can still be unclear if it omits essential 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?

There is no output schema, no annotations, and no explanation of the expected output format ('connection methods'). The description does not state whether one or multiple parameters are required, which parameters map to which task types, or what an agent should do with the returned connection methods.

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 each parameter has a schema description, the descriptions are cryptic and inconsistent: e.g., 'Git ref name; discarded after the shape check' and 'Search text; discarded after the length check'. They do not explain how or whether a parameter should be supplied to accomplish the tool's stated purpose of finding a tool gateway.

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 verb 'Find' and object 'public pay-per-call tool gateway' are present, but the description does not clearly define what a 'gateway' is, what 'connection methods' means, or how a task such as weather/search/scrape/voice is specified. The added sentence 'Task text discarded' further obscures the intended input/output behavior.

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 given about when to use this tool instead of sibling tools. There is no mention of conditions, alternatives, or decision criteria, leaving an agent unable to determine whether this is the appropriate tool for a given request.

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