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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description goes further by naming the specific data classes it never reads or returns, including member records, appointments, payments, attendance/service history, trainers, notes, health details, and record linkages. This adds meaningful behavioral context 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?

Two sentences, zero filler. The first sentence front-loads the tool's purpose and scope; the second sentence lists exclusions that are directly relevant to correct selection. Every clause earns its place, and the structure makes the tool's bounded nature immediately apparent.

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 single-parameter tool with a rich output schema and strong annotations, the description is complete: it states what the overview contains, what it never contains, and that it is bounded. An agent has enough information to decide whether this tool satisfies a request and to invoke it with the correct gymId. No critical operational gap is evident.

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 100%; the gymId parameter is already documented as 'Owned GymFlexa gym id to render' with a strict pattern. The description reinforces the 'tenant-owned' and 'render' semantics but does not add meaning beyond what the input schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Render a bounded administrative overview for one tenant-owned GymFlexa gym.' It distinguishes itself from siblings by enumerating exactly which data categories are combined (safe gym metadata, aggregate schedule counts, service-catalog previews, bookable-capacity counts) and which it never touches, making its scope clear relative to the sibling get_* tools.

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 clearly implies when to use this tool: when a combined administrative overview is needed. It also provides useful negative guidance, explicitly stating it never returns member records, appointments, payments, or service history, which implies those needs should go to other tools. It does not name alternatives explicitly, but the context signals and exclusions are enough for an agent to route correctly.

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