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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: results are grouped by organization, and an empty share list produces a message explaining how the merchant can share apps, with the explicit caution not to tell them they have no apps. The agent's downstream action is also specified. It does not describe pagination or per-app fields, which keeps this just short of a 5.

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?

Front-loaded with the core action in the first sentence, then the decision workflow and the empty-result caveat in order of importance. It is somewhat long because it embeds agent workflow guidance, but nearly every sentence carries a distinct instruction or constraint rather than restating the name.

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 zero parameters, rich annotations, and an output schema already defining the return shape, the description does not need to explain fields. What an agent still needs — when to call it, what to do with the result, and how to handle the empty case — is all present.

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 no parameters, so there is no parameter meaning to convey; the baseline of 4 applies. Nothing in the description contradicts or misdescribes the empty argument object.

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 ('List the Twinr apps the merchant shared with this connection'), plus the grouping semantics ('grouped by organization') and the connection scope. This clearly separates it from sibling get_app, which presumably fetches one app by id.

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 an explicit trigger condition (no application_id in the project's Twinr section), the required follow-up workflow (show every organization and app, ask the merchant, then record the choice), and explicit prohibitions ('Never choose one yourself, and never infer it from the project's name or URL'). This is when-to-use, when-not, and alternatives all in one.

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