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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses what the payload contains (credits, missing fields, human-approval vs auto-publish mode) and the cross-tool dependency that create_release populates the press contact. It does not mention pagination or caching, but for a zero-arg read there is little else to disclose.

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?

A single front-loaded sentence whose opening clause ('Shows the signed-in LivePublicator account') establishes purpose immediately, followed by an enumerated payload list where each clause earns its place. It is dense and comma-heavy, reading as a run-on, but nothing is filler.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so field by field. Combined with the 'call once before drafting' timing rule and the create_release dependency note, an agent has everything needed to call it correctly and to interpret the result.

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 no parameters, so per the rubric the baseline is 4. The description correctly adds no parameter information, and instead spends its words on return semantics, which is the right trade-off here.

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 and resource ('Shows the signed-in LivePublicator account') and then enumerates the exact contents returned: company, saved press contact and spokesperson, missing items, credits, release-approval mode, and agency client companies. No sibling tool reads account state, so it is trivially distinguishable from create_release, list_releases, etc.

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?

Gives a clear directive with a condition: 'Call it once before drafting,' which ties invocation to the drafting workflow that the sibling create_release belongs to. It also warns 'do not ask the user for them' because create_release fills the contact fields. It stops short of naming when not to call it or an alternative source for the same data.

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