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

readOnlyHint=true already covers the safety profile, and the description adds useful behavioral context: it is a cheap call, it acts as a token validity check, and it returns provider ids used as configuration. It does not describe failure behavior (e.g. what an invalid token returns), which keeps it out of the top band.

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?

One dense sentence with the return contents front-loaded, followed by the use cases and the endpoint. No filler and nothing 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?

For a zero-parameter, read-only lookup with no output schema, the description conveys what comes back (application, reachable businesses, their numeric ids) sufficiently for an agent to call and rely on it. A little more on error semantics would make it complete.

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 the schema baseline is 4. The description appropriately focuses on the returned provider id rather than any input, and introduces no phantom parameters.

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?

Specific verb (show) plus a precise resource: the API application the token belongs to and the businesses/providers it can reach, including numeric ids. It is unmistakably distinct from the customer/event/invoice siblings, and it even cites the underlying endpoint (GET /auth/application).

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 two concrete reasons to call it: confirm the token works and discover the value for GOTEAMUP_PROVIDER_ID. It names no sibling alternative, but none exists for this purpose, so little is left to inference; only an explicit when-not clause is missing.

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