Get service bulletins

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds nothing beyond that: no return format, no rate limits, no note on what 'openWorld' means for the upstream feed, and no hint about how the two parameters interact.

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?

It is one short sentence, but the trailing 'using getservicebulletins' is pure redundancy that adds no value. Brevity here stems from under-specification rather than disciplined editing.

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 two undocumented-in-description parameters, one unexplained param name, no output schema, and a feed-based open-world data source, the definition leaves the agent without enough context to call the tool confidently. The surrounding structure does not fill the 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?

Schema description coverage is only 50% – 'rt' is documented as 'Optional route filter' but 'rtpidatafeed' has no description at all. The description text provides no compensating detail, so the meaning of rtpidatafeed remains entirely opaque.

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 essentially restates the name and title: 'Fetch service bulletins using getservicebulletins' adds no information beyond the tool identifier. It does not differentiate this tool from siblings such as prt_get_routes, prt_get_predictions, or prt_get_stops, nor does it clarify what a 'service bulletin' is in this API's context.

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?

There is no guidance on when to use this tool versus the six sibling getters, no mention of prerequisites, and no note on whether filters are applied server-side. The only implicit signal is that it retrieves bulletins, which the name already conveys.

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