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

The description goes beyond the annotations by disclosing the return value (a shareable URL for collaboration) and the optional auto-population of state representatives. Annotations already indicate a non-read-only, non-idempotent operation, and the description adds meaningful behavioral context without contradicting them. It does not address rate limits or duplicate creation, but the annotations cover the safety profile.

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 description is concise at two sentences, with the core action front-loaded ('Create a citizen bridge page'). It efficiently conveys the workspace purpose, return value, and optional behavior without redundant detail, making every sentence value-adding.

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?

Given the tool's moderate complexity (3 optional params, no output schema), the description is sufficient for an agent to invoke it correctly. It specifies what is created, what is returned (shareable URL), and the optional auto-population behavior, covering the essential aspects needed for correct usage.

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 input schema already fully describes all three parameters (zip, state, topics) with 100% coverage. The description's mention of auto-populating representatives adds a bit of context but does not materially improve understanding beyond the schema, which already states that state 'auto-adds federal representatives' and zip is for 'precise district matching'. Therefore the baseline score of 3 is appropriate.

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?

The description clearly states the action ('Create') and the resource ('citizen bridge page'), and explains its purpose as a personalized workspace for tracking representatives, comparing positions, and taking action. It also distinguishes itself from sibling tools like politics_bridge_compare and politics_bridge_letter by focusing on the creation of the workspace itself.

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?

The description provides clear context: use this to create a new bridge workspace and get a shareable URL. It implies a distinct role among sibling tools but does not explicitly mention alternatives or when-not-to-use scenarios. It also notes an optional behavior (auto-populating representatives) that helps in understanding when it might be used.

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