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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to repeat that. It adds useful return-content context by mentioning desk payments, receipt links, photo, and whether the viewer may record memberships, but it does not cover error behavior, permissions required to call it, or pagination.

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?

The description is a single compact sentence with no wasted text. However, because it is a fragment listing returned data rather than a front-loaded action statement, its structure is serviceable but not ideal.

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?

With no output schema, the description should explain the return values, and it does list several key pieces of the gym member record. It remains incomplete for a two-parameter retrieval tool because it does not clarify the missing clientId parameter or explain usage in relation to the many sibling get tools.

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 50%: organizationId is documented as the gym id from list_my_organizations, while clientId has no schema description. The tool description does not mention either parameter or clarify the missing clientId semantics, so it does not compensate for the gap.

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 identifies the resource contents (desk payments, receipt links, photo, and a permission flag) but is a noun phrase without a clear action verb such as retrieve or get. The tool name supplies the verb, but the description itself does not fully state what the tool does.

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 description gives no indication of when to use this tool, when not to use it, or which sibling tool to choose instead. It simply lists data associated with a gym member record.

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