get_master

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only a conceptual definition of the resource and says nothing operational beyond that – no auth expectations, no note on what data (image flag, formats) is affected by the parameters.

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 a single short sentence with no wasted words, but it is under-specified rather than tight: it leads with a noun definition instead of the action. Concise but not front-loaded with what the tool does.

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 tool with no output schema the bar is modest, yet the definition omits the action, the meaning of include_images, and any sense of the returned payload. An agent cannot call this confidently without guessing at the parameters.

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 0%, so the description should compensate for the two undocumented parameters. It explains nothing about master_id or include_images, leaving both entirely to field names. Only indirect value is the loose link between 'master' and master_id.

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 defines what a 'master release' is ('the umbrella over every version/pressing of an album') but never states the action the tool performs. It gives a resource definition rather than a verb+resource, so the agent must infer that this retrieves a single master. It offers partial differentiation from get_master_versions by framing the master as the umbrella over versions, but not explicitly.

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 when-to-use guidance and no reference to alternatives such as get_release or get_master_versions. The agent is left to infer the correct tool purely from the name.

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