get_gp_advisor

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

In absence of annotations, description discloses key behaviors: lists cities with matching district, distance, yield, and great work slot availability. Ranking mentioned but not detailed; non-destructive implied.

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?

Two concise paragraphs, first sentence encapsulates purpose, Args line specifies input, then details output content. No wasted words.

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?

With output schema present, description covers input, purpose, and key output aspects. Could mention that GP must be owned, but adequate for a single-param tool.

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?

Adds critical context for unit_index parameter: 'from get_units output', which schema alone (integer) does not provide. Schema coverage 0% makes description essential.

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?

Description clearly states verb 'Show' and resource 'best cities to activate a Great Person', ranked by suitability. Distinct from sibling tools like get_cities and get_district_advisor.

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?

Implicitly guides usage by requiring unit_index from get_units output, and lists what information is shown. Lacks explicit alternatives or when-not-to-use, but clear enough for agent.

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