septa_alerts

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

The annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds useful return content types (messages, advisories, detours, snow alerts) and implies real-time current status, but it does not disclose update frequency, format, or behavior when no alerts exist.

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 two tight sentences with the primary action front-loaded. Every clause adds value: scope, route coverage, and return content. No filler or redundancy.

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 no-parameter, read-only alerts tool, the description covers the main purpose and output categories sufficiently. It does not explain update cadence or output structure, but given the simplicity and lack of output schema, the information provided is reasonably complete.

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?

The tool has zero parameters, so there is no parameter semantics to clarify. The description's mention of 'all SEPTA transit routes' reinforces that no filtering or input is needed, making this appropriate for a parameterless tool.

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 clearly identifies the tool as fetching service alerts for SEPTA transit routes, specifying the geographic scope (Philadelphia) and all routes. It distinguishes well from sibling tools like septa_train_view and septa_bus_view by focusing on alerts rather than schedules or vehicle positions.

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 implies use when current SEPTA service alerts are needed, covering messages, advisories, detours, and snow alerts. It does not explicitly mention alternatives or when not to use it, but the purpose is specific enough that an agent would not confuse it with other transit tools.

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