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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description's one added behavioral fact is that no sign-in is required, which is genuinely useful auth context, but it says nothing about failure behavior for an invalid/unknown id, rate limits, or what the verification verdict looks like.

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?

Two sentences: the first front-loads the core action, the second gives the motivating scenario. No filler, no repetition of the title, and the size matches the tool's simplicity.

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 no output schema, the description partially compensates by saying you can 'see what it concluded', hinting at a verdict/result payload. It is nearly complete for a one-parameter read tool, though it leaves the exact return shape and unknown-id behavior unstated.

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?

There is a single required parameter with 100% schema description coverage, including an example id format, so the schema does the heavy lifting. The description adds no format, validation, or lookup semantics for report_id beyond what the schema already provides.

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 states a specific verb and resource: check that a MusicCheck report id refers to a real screening and report what it concluded. That is distinct from retrieving a screening for internal use, but it never names get_screening or otherwise differentiates itself from the sibling that also takes a screening/report identifier.

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?

It gives a concrete usage context — anyone can verify a report someone else shows them, e.g. a claim of 'already cleared' — which tells the agent this is the tool for third-party authenticity checks. It stops short of naming alternatives (get_screening) or stating when not to use this tool.

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