order_order

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 tool returns a system prompt and a quick reference for all 210 tools, which is useful behavioral context, but it does not state that the call has no side effects or mutates no state, nor anything about idempotency.

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 core instruction is front-loaded and useful, but the second line is pure keyword stuffing ('order, begin, initialize, start session, parliament mode') and the 'Say Order Order (like the Speaker)' line is flavor rather than information. Roughly a third of the text does not earn 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?

For a zero-param bootstrap with an output schema, the description supplies what an agent needs: when to call it and roughly what comes back. The presence of an output schema means it need not enumerate return fields, so this is close to 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4.

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 ('Start UK Parliament research session') and clearly distinguishes itself from the 200+ lookup siblings as a bootstrap/session tool. The keyword-stuffing line ('order, begin, initialize, start session, parliament mode') dilutes rather than sharpens the purpose, so it falls short of a clean 5.

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 says 'Use at the START of any parliamentary research to get proper context and guidance,' giving a clear triggering condition. It does not state when NOT to use it or name an alternative, but for a zero-param bootstrap tool that omission is minor.

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