Get a Schedule

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

No annotations are provided, and the description focuses only on purpose. It does not disclose behavioral traits such as read-only nature, auth requirements, or side effects, though the tool appears to be a simple read.

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 two sentences, clearly structured with the primary purpose first, then details about each schedule. No unnecessary words.

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 simple tool with one parameter and no output schema, the description provides sufficient context about each schedule's content, making it complete for an agent to use correctly.

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 has 100% coverage with a description for the 'number' parameter. The tool description adds meaning by mapping schedule numbers to their content, going beyond the schema's basic range.

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 specifies 'Return a Schedule of the Prediction Market Regulations 2026' and details each schedule's content, clearly distinguishing it from sibling tools like get_authorisation_conditions or get_regulation.

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 implies usage when a specific schedule is needed but does not explicitly state when to choose this over alternatives like get_authorisation_conditions, which could overlap with Schedule 2.

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