get_music_entitlements

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

Annotations already cover safety (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description adds meaningful context that supports them: the backend may initialize first-use entitlements, which explains why a 'get' is not purely read-only. It also discloses that music_credits are internal settlement data that must not be surfaced, which is genuine behavioral guidance beyond the annotations.

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?

Three tight sentences with the purpose front-loaded and the most consequential constraint ('must not be shown even when nonzero') given emphasis. Every sentence carries a distinct instruction, though the display rule borders on presentation policy rather than tool semantics.

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 zero-parameter tool with no output schema, the description supplies purpose, a data-handling rule, and a side-effect caveat. It could go slightly further by hinting at what a successful response contains (e.g., universal credit fields), but it is largely 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?

The tool takes zero parameters, so the 4-point baseline applies. There is nothing for the description to add, and it correctly does not invent parameter semantics.

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?

States a specific verb+resource ('Query music entitlements'), which cleanly distinguishes it from the parallel get_video_entitlements and get_speech_entitlements siblings by resource domain. It lacks any explicit differentiation text, but the resource name carries the distinction.

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 indication of when to call this tool versus the sibling entitlement tools, nor any stated preconditions or ordering (e.g., before generate_music or estimate_music_cost). The display instructions govern result presentation rather than tool selection.

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