query__country

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, but "[QUERY]" only suggests a read-style operation. It does not disclose authentication needs, required argument behavior, return shape, or any other behavioral traits an agent would need to invoke it confidently.

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 but under-specified rather than appropriately concise. It is a single unhelpful phrase with no structure, no context, and no explanatory value for an agent.

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?

This tool has four parameters, one required field, nested objects, and ambiguous sibling relationships, yet the description provides none of the context needed to select or call it correctly. It is effectively a stub.

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%, and the schema already documents `code`, `__fields`, `bearer_token`, and `custom_headers`. The description adds no parameter meaning, but per the high-coverage baseline, it does not need to compensate.

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] country" is a tautology that restates the tool name without explaining what querying a country returns, how it is identified, or how it differs from query__countries or execute_graphql. It identifies a resource and a generic operation, but stops short of a usable purpose statement.

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 siblings like query__countries or execute_graphql. There is no mention of prerequisites, alternative tools, or conditions such as needing a specific country code.

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