get_constituency_synopsis

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

No annotations are provided, so the description carries the full burden. It does disclose that the output is a text synopsis, implying a safe read, but says nothing about permissions, error behavior, or whether the synopsis may be absent for some constituencies.

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 pipe-delimited keyword list ('constituency overview, constituency description, area summary') and the Args/Returns block pad the text with synonyms and repeat 'synopsis' several times. It is front-loaded and readable, but not every clause earns its place.

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?

An output schema exists, so return values need not be re-explained (though the description redundantly does so). For a single-parameter read tool with no annotations, the definition covers the essentials, though it omits any sibling routing that this crowded namespace would benefit from.

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 compensate, and it does: 'constituency_id: Unique constituency ID number.' This documents the single parameter's identity and type, which the bare integer schema does not. It is minimal but adequate for one required param.

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 (Get) and resource (constituency synopsis) and clarifies the return is a text synopsis. However, it does not distinguish itself from the many sibling constituency tools (get_constituency_by_id, get_constituencies, get_constituency_representations) that an agent must choose between.

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?

Provides a positive usage cue ('Use when you need a concise description or background information about a constituency'), which is more than nothing. But it offers no when-not guidance and names no alternative tool, so the agent must infer why to pick this over get_constituency_by_id.

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