get_opposition_posts

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 the operation's nature and scope (a read of 'all current' posts, returning holders with member details), which is adequate for a no-argument list endpoint, but says nothing about permissions, volume, or how 'current' is determined.

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 synonym keywords are front-loaded, which is good, but the core statement is duplicated: 'List all current opposition frontbench positions with their holders' and the trailing 'Returns: List of opposition frontbench positions with current holders' say the same thing. The pipe-delimited layout also reads like stitched-together metadata rather than prose.

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 parameterless read tool with an output schema and no annotations, the description covers purpose, scope, and alternatives sufficiently. The duplicate return sentence is unnecessary given the output schema already defines the payload, but nothing an agent needs in order to call it is missing.

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?

The tool takes zero parameters, so there is nothing parameter-related for the description to clarify; this is the baseline 4 case. The description correctly does not invent options that the empty schema does not support.

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 and resource ('List all current opposition frontbench positions with their holders') and adds retrieval synonyms (shadow cabinet, shadow ministers, opposition frontbench). The word 'opposition' cleanly separates it from the sibling get_government_posts, so an agent can tell the two apart 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?

It points at two alternatives ('See also: get_government_posts, get_spokespersons') but never states the condition that selects one over the other, nor any when-not-to-use cases. The routing intent is implied by the sibling names rather than explained, which is only minimum-viable guidance.

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