query__languages

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

With no annotations, the description carries the full burden of behavioral disclosure. '[QUERY]' weakly implies a read-only operation, but no traits such as pagination, filtering behavior, authentication requirements, or response format are disclosed.

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 short, containing no wasted words, but it is under-specified rather than appropriately concise. It lacks the structure needed to convey meaningful usage.

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 almost no context for a tool with optional parameters, no output schema, and no annotations. It fails to explain what languages are returned, how the filter works, or how this tool relates to sibling query__language and execute_graphql.

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 100%, with each parameter documented including __fields, bearer_token, custom_headers, and filter type. The description adds no extra parameter meaning, but the schema already covers this dimension, so baseline 3 is appropriate.

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 '[QUERY] languages' identifies a query operation on a language resource, which is more than a pure restatement but still vague. It gives no detail on what is returned or how it differs from the sibling query__language beyond plurality.

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?

There is no guidance on when to use this tool versus alternatives. Sibling query__language and query__languages are listed nearby, but the description makes no attempt to distinguish them or explain selection criteria.

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