get_recsports_facilities

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

With no annotations provided, the description carries the full disclosure burden. It accurately states the tool returns facility information including hours, availability, and events, implying a read-only operation. However, it does not detail response format, data completeness, or any limitations.

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 a single sentence of 16 words, efficiently conveying the tool's purpose. No unnecessary words, but it could be slightly more structured with a bullet list if needed.

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 context of many sibling tools and no output schema, the description provides a minimal outline of what is returned (hours, availability, events). However, it lacks details on data structure, pagination, or how this tool differs from its siblings, making it adequate but not fully 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?

There are no parameters, so the baseline is 4. The description effectively communicates that this tool retrieves all facilities without filtering, which compensates for the lack of parameters.

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 tool returns information about all OSU recreation sports facilities, specifying details including hours, availability, and events. However, it does not explicitly distinguish this broad list from more targeted sibling tools like get_facility_details or get_facility_hours, leading to potential ambiguity.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like search_recsports_facilities, get_facility_details, or get_facility_hours, which exist as siblings and might be more appropriate for specific queries.

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