alphaportal_get_bus_location

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

The annotations declare readOnlyHint=true, and the description adds meaningful behavior beyond that: it returns the last known position and returns empty when the bus is not running. This helps set expectations about freshness and empty results, which is valuable for a real-time location tool.

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 that front-loads the core purpose, includes the key returned fields, and adds the empty-state behavior. No words are wasted, and every clause adds distinct value.

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?

For a simple two-parameter read-only tool with no output schema, the description is complete: it states the inputs (student/run), the output fields, and the edge case of the bus not running. The schema covers the remaining required details, and annotations confirm no side effects.

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 the baseline applies. The description's mention of 'selected run (AM or PM)' reinforces the shift parameter semantics, and 'student's bus' aligns with studentId, but it does not add new details beyond what the schema already documents.

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 states a precise verb ('Get') and resource ('live GPS location of a student's bus'), explicitly enumerates returned fields (latitude, longitude, speed, vehicle id), and scopes the operation to AM/PM runs. This clearly distinguishes it from all sibling getters, which retrieve profiles, students, settings, or reports.

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 description clearly indicates when this tool is appropriate: when the agent needs the current GPS position of a student's bus for a specific run. It does not name an alternative or explicit when-not-to-use condition, but no sibling tool offers similar bus-location functionality, so the context is sufficient.

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