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

With no annotations, the description carries the full behavioral burden and discloses that the operation is read-only, the auth prerequisite, the workspace-claim gate, and the specific 403 refusal for sandbox keys. It also notes that experiment status, views, and conversions appear only once the demo workspace is seeded. Pagination and ordering are unmentioned, but there are no parameters anyway.

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 three sentences and front-loads the core purpose and returned fields. The first sentence is dense but every clause earns its place by specifying content and conditional data availability.

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, no-output-schema tool, the description explains both what is returned and the preconditions for a successful call. It is complete enough for an agent to invoke correctly, though it could mention ordering or pagination behavior even without 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?

The tool takes zero parameters, so the baseline is 4. There is no parameter meaning for the description to add or omit.

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 (list the demo apps Last Price ships) and enumerates the returned fields, making the tool's scope unambiguous. An agent can distinguish it from generic experiment or app listings without opening a schema.

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 clear usage context: read-only, requires a Last Price credential, and requires a claimed workspace because a self-registration sandbox key is refused with 403. It does not name a sibling alternative or state explicit when-not-to-use conditions, but the prerequisites are actionable.

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