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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it returns newly added server features without reconnecting, and explains that missing tools are accounted for via unavailableGroups with a reason field — useful behavioral detail for an introspection tool.

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 sentences in Korean, each earning its place: the return value, the ideal invocation timing, and the unavailableGroups detail. It is front-loaded with the core purpose and wastes no words on restating the name or title.

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 introspection tool with no output schema, the description is complete: it explains what is returned, when to call it, and how to interpret missing tools. Annotations cover the safety profile, so nothing an agent needs to invoke it correctly is missing.

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 has 0 parameters, so the baseline is 4. The description adds value by explaining what the return payload contains (identity, permissions, tool list, unavailableGroups.reason), compensating for the absence of an output schema.

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 — it returns the connection's identity, permissions, and the full list of usable tools. It differentiates from all siblings (checkout, product, signup, inquiry tools) by explicitly addressing 'what can I do?' / 'what are my permissions?' questions, so an agent can tell this apart without opening any other definition.

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 gives explicit when-to-use guidance: call once before starting work involving company data, and use it for capability/permission questions. It doesn't name exclusions or alternatives, but the sibling tools are all distinct operations (checkout, product lookup, signup), so the usage context is clear without needing explicit negative guidance.

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