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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description correctly spends its words on data semantics instead: it instructs the agent to retain source/review dates, caveats and canonical links, and warns that issue scales are not current law or assigned politician scores. That is genuine behavior context beyond the annotations, though it says nothing about failure behavior for unknown slugs.

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 compact sentences with the core action and resource list front-loaded, followed by the prerequisite and the data-handling caveats. Every clause carries information; no filler or restatement of the title.

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 read-only, single-record fetch with no output schema, the description adequately characterizes what comes back (dated, sourced, caveated content with canonical links) and warns about the most likely misinterpretation of issue scales. Only the absence of any note on missing-slug or access-check behavior keeps it from being complete.

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 0%, so the description must carry the load, and it does: it ties kind/slug/country to values obtained from search_politics and states the conditional requirement for country that the schema itself does not express (country is optional in the schema). Minor deduction for calling the field 'countrySlug' while the schema property is 'country', which could momentarily confuse an agent.

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 ('Read') plus the exact resource families it covers (party, faction, politician, country-system, issue) and names the sibling tool (search_politics) it is paired with. An agent can immediately distinguish this retrieval tool from search_politics and from get_politics_races without opening a schema.

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?

Explicitly routes discovery to search_politics ('using the exact kind, slug and countrySlug from search_politics') and states the conditional prerequisite that parties, factions and issues require a country. It stops short of naming exclusions (e.g., races belong to get_politics_races, spectrum to get_political_spectrum), so it is clear but not fully exhaustive.

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