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

Annotations already cover read-only safety, but the description adds a meaningful visibility model: account sharing does not imply strategy sharing and strategy sharing never exposes sibling strategies. That is substantive permissions context beyond the structured 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 compact sentences, front-loaded with the verb, with each clause conveying scope or visibility semantics. No filler, though the second sentence is densely packed shorthand.

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?

The read-only tool correctly needs no output schema explanation, and visibility semantics are covered. However, with 3 parameters at 0% schema coverage and a required enum, the relationship between subjectKind and the two ID parameters is left unexplained, which is a real completeness gap for correct invocation.

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 0%, so the description must carry parameter meaning. It vaguely ties 'account or strategy subject' to subjectKind, but never explains that accountId and strategyId are the corresponding identifiers, nor that exactly one should be supplied in line with subjectKind.

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 ('Reads') and resource ('one owner publication'), clearly implying a single-item retrieval distinct from list_my_marketplace_publications. It does not explicitly name that sibling, but the 'one' vs list distinction is inferable.

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?

'using an explicit account or strategy subject' implies the required subjectKind choice but gives no explicit when-to-use guidance and does not name alternatives like list_my_marketplace_publications. Usage is implied rather than spelled out.

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