get_bus_trip_updates

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

No annotations available. Description implies read operation ('Get live... predictions') but does not disclose potential side effects, rate limits, or data freshness. Adequate but not detailed.

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?

Single sentence, no wasted words, front-loaded with key info. Highly concise and efficient.

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?

Simple data retrieval tool with optional parameters. Description covers purpose and data type. Output schema exists (not shown) so return format is handled. Slight lack of context about data freshness or scope (MARTA), but overall sufficient.

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?

Input schema has 100% parameter description coverage. Description adds no extra meaning beyond schema fields; baseline score of 3 applies.

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?

Clear verb 'Get' and specific resource 'live MARTA bus arrival/departure predictions' with format mention. Distinct from siblings (bus positions, rail, stations).

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 on when to use vs siblings or alternatives. Only states what tool does; no explicit when/when-not or exclusion context.

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