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.