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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by enumerating what the tool will NOT do (no creation, switching, uploads, generation), preventing an agent from expecting side effects. It stops short of saying what happens if the connection is unauthenticated or has no profile.

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?

Three short sentences, zero filler, with the positive statement front-loaded, the negative scope second, and the sibling routing last. Every sentence earns its place.

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 an output schema and full annotation coverage, the description does not need to explain return values or safety. What remains thin is the meaning of 'stable profile' — an agent knows to call it but not precisely what identity fields come back. Adequate for a zero-argument, read-only lookup.

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?

Zero parameters, so there is nothing about inputs to explain; baseline is 4. The description appropriately spends no words on input semantics.

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?

States a specific verb and resource (read the stable profile of this connection) and scopes it against siblings by naming get_trifit_account. 'Stable profile' is somewhat abstract — it never says what a profile contains — but combined with the title and the routing sentence an agent can tell what this returns.

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 final sentence explicitly routes the agent to get_trifit_account for connection mode and allowance source, which is real when-to-use guidance. No explicit exclusion list beyond that, but the negative-scope sentence ('No account creation, switching, uploads or generation') guards against the most likely misuse.

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