get_neutral_territories

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

There are no annotations, so the description carries the behavioral burden. The verb 'find' reasonably implies a read-only lookup, and 'claimable' adds context about the result set. However, the description does not mention whether state changes occur, how results are ordered, or what territory information is returned.

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 one compact sentence with no filler. It front-loads the core purpose and includes the key selection criteria: claimable, neutral, and near kingdom.

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?

For a simple one-parameter getter, the description is nearly sufficient, but there is no output schema and the description does not say whether the tool returns a list, what fields a territory includes, or what the agent should do after finding one. These are moderate gaps given the absence of any other behavioral or output documentation.

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?

There is exactly one parameter and the schema description coverage is 100%, so the schema already explains that api_key is required and what it is for. The tool description adds nothing beyond the schema, which is acceptable given the baseline for full schema coverage.

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 identifies the operation and resource: find claimable neutral territories, with the important qualifiers 'claimable' and 'near your kingdom'. It is clear, but it does not explicitly distinguish itself from related sibling tools such as inspect_territory or claim_territory.

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?

The description implies when to use this tool: when the agent wants to discover neutral territories available for claiming near a kingdom. It offers no explicit when-not-to-use guidance and does not point the agent to claim_territory or inspect_territory as alternatives.

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