get-metadata-ui

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

With no annotations, the description carries the burden: it correctly signals a read of draft state and implies a signed-in browser session (reinforced by the headless first-sign-in parameter). It does not state what happens when not signed in, whether a browser is launched, or what is returned for unset fields.

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 tight sentences: the scope of the read first, then the draft-vs-published caveat front-loaded before any schema detail. Nothing is wasted and nothing essential is deferred.

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 read tool with no annotations and no output schema, the description covers what is read and from where, but leaves the return shape, empty-field behavior, and sign-in failure mode unexplained. Those gaps matter for a browser-driven tool whose headless/accountIndex params imply session dependencies.

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 100%, so itemId, headless and accountIndex are already fully documented. The description adds no meaning about how those parameters affect the read, which is acceptable at baseline 3 when the schema does the work.

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 (Read) and an enumerated resource (draft listing description, category, homepage, support URL) from a named source (the signed-in Developer Dashboard). The clause 'This is not the published listing' distinguishes it from the published-listing sibling, so an agent can select it 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?

The draft-vs-published distinction gives a clear context for use: call this to inspect the unpublished draft rather than live listing data. It stops short of naming the sibling to use for the published listing (likely 'get') or of stating prerequisites such as being signed in, so it is clear but not exhaustive.

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