Bookable campus services

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new behavioral context: results are live/scoped to the current moment and can vary by time of day, so an agent learns that absence of Click & Collect in the morning-window is expected rather than an error.

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?

Two short sentences: the first front-loads purpose with examples, the second adds a single operational caveat. Nothing is redundant or buried.

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?

With no output schema and no parameters, the description carries the burden of explaining what comes back. It implies a list of services but never indicates whether items carry identifiers needed for the downstream resto_order_offer / resto_order_prepare flow, or whether authentication via edhec_login is required.

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; baseline applies. No misleading parameter hints are given.

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-less but clear resource: services bookable through MONEWEB, with concrete examples (Click & Collect, sport classes, sport shop). An agent knows it returns a catalogue of bookable items, though the description does not explicitly distinguish it from siblings like resto_menu or resto_order_offer.

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 phrase "right now" and the note that Click & Collect only appears while ordering is open (mornings) imply this is the entry point for seeing current availability, which is useful timing guidance. However, it never says when to use this versus resto_menu, resto_order_offer or resto_order_prepare, leaving the workflow routing to inference.

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