find_sessions

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

The annotations already disclose that this is read-only and open-world, and the description adds source context. However, it does not describe behavioral details such as whether location parameters are filtering or required, whether results are live or cached, or how the OpenActive feeds are consumed. There is no contradiction with the annotations.

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, scannable phrase with no filler and places the core resource type first. It is appropriately terse, though this terseness contributes to the lack of usage and parameter guidance.

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 an output schema, read-only and open-world annotations, and all optional parameters, the description does not need to explain return values. But it omits meaningful context such as default behavior without location, what ORP/OpenActive mean in practice, and how this differs from find_facilities, leaving a moderate gap.

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?

Only the activity parameter has a schema description, giving 20% schema coverage, and the description adds no parameter guidance. The agent must rely on parameter names and constraint ranges, so the description does not compensate for the low coverage.

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 identifies the resource as 'classes and bookable facility slots' and names specific sources ('ORP provider manifests and OpenActive feeds'). It is clear, but it relies on the tool name for the verb and does not explicitly contrast itself with the sibling find_facilities.

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 guidance is given about when to use find_sessions versus alternatives such as find_facilities or geocode. The intended use must be inferred entirely from the resource type.

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