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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds real substance beyond them: the payload includes source dates, axes, caveats, chartAvailable and articleMarkdown, and that coordinates are editorial estimates rather than measured ideology. The null-is-unknown-not-center note is a valuable semantic caveat. It stops short of describing shape/size of the politician dataset or any limits on coverage.

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?

Front-loaded with the core purpose and packed with useful detail in only a few sentences; nearly every clause carries information (slug source, edge case, returned fields, chart embedding, coordinate caveat). The sentences are long and run together, and the '567politics' branding garble slightly blunts the opening.

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 single-parameter, read-only lookup with no output schema, the description covers what comes back, an important edge case (closed dictatorships), how to use a returned field downstream, and a critical interpretive caveat about coordinates. An agent has everything needed to call and interpret it correctly.

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 coverage is 0%, so the description must carry the parameter, and it does: 'country' is defined as a slug sourced from search_politics, which tells the agent where to obtain the value and roughly what format to expect. It does not spell out the lowercase-hyphen pattern or the 200-character bound, but the essential meaning is supplied.

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?

States a specific verb+resource: reading party/faction positions and independently sourced politician placements on a political spectrum for a supported electoral system. It implicitly separates itself from siblings by pointing to search_politics for slugs and noting that closed dictatorships return profiles/context only (i.e., get_politics_profile territory). The brand-mangled opening ('Read 567politics selected party/faction positions') is slightly awkward but the intent is still clear.

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?

Gives an explicit prerequisite/entry point: 'Use the country slug from search_politics', and carves out the case where only profiles/context exist. It also explains how to consume the output for chart embedding. It does not explicitly compare against get_politics_races or get_politics_profile by name, so the routing guidance is clear but not exhaustive.

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