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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds the payload composition, which helps an agent decide whether a fetch is worth it, but it says nothing about missing/invalid IDs, external Wikipedia dependency timing, or freshness of listener stats.

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?

A single front-loaded sentence with no filler; every clause contributes either the action or a category of returned data.

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 an output schema present the description need not explain return values, and one fully documented parameter plus strong annotations leaves little uncovered. Only edge-case behavior for an unknown ID is unaddressed.

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% and the schema itself gives the 12-character hex form plus a slug-id example. The description's 'by ID or slug-id' restates that rather than adding new meaning, so 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?

Specific verb ('Get') plus resource ('detailed profile of a station') and an enumeration of what the profile contains (broadcast metadata, Wikipedia summary, listener stats, similar stations). It is clearly distinguishable from search_stations and get_now_playing, though it never names a sibling to contrast against.

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 phrase 'by ID or slug-id' implicitly tells the agent this is the lookup tool for when you already hold an identifier, which is the practical discriminator versus search_stations. There are no explicit exclusions or stated preconditions, so it stops short of full routing guidance.

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