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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds genuinely new behavioral facts: identity is resolved from the connection, no arguments are accepted, results are capped at 50 catalogues, and the call is 'Free'. The 50-catalogue cap and the cost note are meaningful beyond the annotations.

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?

Four short sentences, front-loaded with purpose, followed by return shape, argument constraint, and cost. No sentence is redundant and nothing is buried.

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?

An output schema exists, so return details need not be expanded, and annotations carry the safety profile. For a zero-parameter read tool the description covers identity resolution, result bounds, and cost, leaving no gap an agent needs to fill before calling it.

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?

With zero parameters the baseline is 4, and the description adds relevant meaning by stating that identity comes from the connection and that no account/workspace argument is accepted, explaining why the schema is empty.

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 gives a specific verb and resource ('Read the connected customer account and its current catalogue memberships') and states what is returned (user details plus up to 50 catalogues with roles). It is clearly distinct from most siblings, though it never explicitly names the near-neighbour studio_account_links_read to disambiguate.

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?

Usage is implied by the scope ('the connected customer account'), and the note that 'no account or workspace argument is accepted' constrains invocation. However, there is no explicit when-to-use guidance and no alternative tool is named, so the agent must infer this from the scope statement alone.

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