mbta_get_schedules_by_time

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

No annotations provided; description only restates filtering purpose without disclosing behavioral traits like pagination, default limits, or read-only nature. Schema includes page_limit default but description adds no transparency beyond that.

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 efficient sentences, front-loaded with action and then usage context. No wasted 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?

With 8 optional parameters and no output schema, the description lacks details on return structure, behavior with no filters, or interaction between parameters. Incomplete for a complex filter tool.

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?

Schema description coverage is 100%, so description adds minimal semantic value beyond reinforcing filtering by times/dates. Baseline 3 is appropriate.

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?

Description clearly states 'Get MBTA schedules filtered by specific times and dates' and 'Use this to find transit schedules for particular time windows, dates, or specific trips.' It distinguishes from sibling 'mbta_get_schedules' which likely provides unfiltered schedules.

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?

Implies usage for time and date filtering, but no explicit guidance on when not to use or alternative tools like mbta_get_schedules for broader queries.

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