PENNY — Sovereign Music Delivery

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

With no annotations, the description carries the full burden and does well: it discloses that tracks are pulled server-side from public share links (nothing uploads from the agent), that contentOrigin is required and permanent, that missing ISRCs are auto-assigned at finalize, and that delivery is free with no exclusivity and retained rights. It omits auth/permission requirements and rate limits, which keeps it from a 5.

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 purpose and accepted release types are front-loaded in the first sentence, followed by tightly packed disclosures about sourcing, contentOrigin, ISRC handling, and returns. Every sentence carries distinct, non-redundant information with no filler.

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 an 8-parameter mutation tool with no output schema and no annotations, the description covers sourcing mechanics, required fields, ISRC behavior, rights terms, and the return payload (releaseId and live status). Missing only operational concerns like permissions/limits, so it is nearly but not fully 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?

Schema coverage is 63%, and the description meaningfully supplements it: contentOrigin is called out as REQUIRED and permanent with its enum values, sourceUrl is constrained to public https share links, and the ISRC auto-assignment behavior for the tracks array is explained. It adds real semantics beyond the field descriptions.

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 (Deliver) and resource (a release) and enumerates the release kinds it accepts (single, album, EP, podcast episodes, spoken word, audiobook). It is clearly distinguishable from the sibling tools, which are status/key/info utilities rather than a delivery action.

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 implies context (free window, returns releaseId and live status) but never states when to use this tool versus penny_delivery_status or penny_platform_info, nor any preconditions for calling it. Usage is inferable but not spelled out.

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

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

With no annotations, the description carries the full burden, but 'Check' implies a read and the lifecycle enumeration (received → minting → live) usefully discloses the state machine and expected return fields. It says nothing about behavior for an unknown releaseId, auth requirements, or side effects, so meaningful gaps remain.

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 compact sentence that front-loads the action and identifier, then enumerates the returned fields. Nothing is padded or redundant.

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 one-parameter read tool with no output schema, the description covers the core return payload (status, title, artist). Only edge-case behavior (not-found, in-flight polling cadence) is missing, which is a minor gap at this complexity level.

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 coverage is 0% for the single releaseId parameter, so the description must compensate. 'By releaseId' confirms it is a lookup key rather than a filter or free-text query, which is minimal added value beyond the self-explanatory name.

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 (Check) and resource (delivery) plus the key returned fields (lifecycle status, title, artist), so the agent knows exactly what this tool retrieves. It doesn't explicitly contrast itself with penny_deliver_release, but the read-vs-submit distinction is inferable from the verb.

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?

No when-to-use guidance, no mention of when not to use it, and no reference to the sibling penny_deliver_release or penny_platform_info. The agent must infer that this is the polling/lookup counterpart to penny_deliver_release entirely on its own.

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

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the key is public, valid until the window closes, and minting or using it accepts detailed delivery terms including pricing, reporting, payment, and takedown obligations. It still omits operational details such as authentication requirements, rate limits, and failure behavior, so it is not fully complete.

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 front-loaded with the return value and validity, then moves to usage and legal terms. The legal-terms sentence is dense, but the content is relevant to acceptance and is not wasted.

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?

Given no output schema and no annotations, the description explains what is returned, how long it is valid, how to use it, and the legal implications of minting or using it. It is adequate for a zero-parameter key-minting tool, though it could mention error behavior or response format more explicitly.

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 baseline is 4. There are no parameter semantics for the description to clarify beyond the schema.

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: it returns the public free-window access key for FAST PASS DISTRO delivery, and it specifies the key's validity. It does not explicitly differentiate this tool from the sibling delivery tools, so it falls short of a 5.

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 explains how to use the returned key, either as X-Api-Key against /api/v1/b2b-ingest/* or by handing it to a human for the Fastpass URL. However, it does not say when to call this tool instead of siblings like penny_deliver_release or penny_delivery_status, and it gives no exclusions or prerequisites.

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

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

No annotations are provided, so the description carries the full burden. It discloses the tool's return contents and the contentOrigin transparency policy, but it does not state whether the operation is read-only, whether any side effects exist, or other operational constraints.

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 compact and front-loads the core identity before listing return values. The pricing and royalty details are contextual rather than strictly necessary for invocation, but they are brief and do not obscure the main action.

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 parameterless information tool with no output schema, the description adequately explains what is returned: platform facts, free-delivery window state, and transparency rules. The main missing piece is routing guidance relative to sibling tools.

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 are no parameter semantics to document. The baseline for a parameterless tool is 4, and the description adds relevant context about what the operation returns.

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 uses a clear verb, 'Returns,' and enumerates the resources: platform facts, the free-delivery window state, and transparency rules. It is specific enough to tell what the tool does, though it does not explicitly differentiate itself from sibling tools such as penny_delivery_status or penny_free_window_key.

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 explicit guidance on when to use this tool versus the sibling tools. The description implies it is the general platform-information tool, but it does not state when-not to use it or route the agent to a more specific alternative.

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