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

Beyond the readOnly/openWorld annotations, it discloses a real auth prerequisite ('needs a connected Phorme account') and a data-gating behavior: free listings return only a little reach and what was missed, with the rest locked like the web console. That tier behavior materially affects how an agent should interpret results. The 'reads only and changes nothing' line is largely redundant with readOnlyHint=true.

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 trigger condition is front-loaded, followed by return contents and then the free-tier caveat and auth note. It is a bit dense in the middle where it enumerates many metrics, but every clause carries information an agent can act on.

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 already exists, yet the description still conveys the access-gating and auth requirements an agent needs to set expectations. Combined with the annotations, nothing essential is missing for a zero-parameter read tool.

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 zero parameters, so there is nothing for the description to disambiguate — baseline 4 applies. The description correctly indicates the report is implicitly scoped to the connected account rather than requiring any argument.

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 names a specific verb and resource — it returns each place the connected account lists, with page, status, and a report of metrics. It also scopes the audience ('gym, studio or clinic owner... their own places on Phorme'), which separates it from the coaching-oriented sibling get_my_coaching_business.

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?

It gives explicit trigger conditions and two example user utterances ('how is my gym doing on Phorme?', 'did anyone book this week?'), making the use case easy to match. It stops short of naming a specific alternative tool or stating when not to use it, so it is clear context without exclusions.

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