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

Consistent with readOnlyHint=true, and it adds behavior beyond the annotations: the required merchant:manage scope and the fact that unpublished/paused settings are visible in the response. It stops short of describing the response shape or any rate/visibility limits, but the added auth and content-scope details are substantive.

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 short sentences with zero padding. The resource and scope come first, with the auth prerequisite trailing, which is the right front-loading for a read tool.

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 read-only tool with no output schema, the description covers what is returned at a high level (profile including unpublished/paused settings) and the permission gate. It does not sketch the returned fields, which would be the only remaining gap.

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 and the input schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter information is needed or missing.

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 resource (your worker profile) and adds the scope qualifier that unpublished or paused settings are included. The possessive 'your' implicitly distinguishes it from the sibling get_worker_profile, but the description never names that sibling, so the differentiation must be inferred.

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 auth prerequisite (merchant:manage) gives a concrete gating condition for use, which is useful. However, there is no explicit guidance on when to prefer this over get_worker_profile or when to use set_worker_profile instead, so the usage context is only implied.

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