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 still adds value by scoping the read to the authenticated actor and enumerating the returned facets (label, organization, role, modules). It does not discuss auth prerequisites or failure modes, keeping it 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?

Two sentences, both load-bearing: the first establishes purpose and trigger, the second establishes the negative boundary. No redundancy with the title or schema.

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 tool with rich annotations and a declared output schema, this description covers trigger, scope, and exclusions. Nothing additional is needed for correct invocation.

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 to disambiguate; baseline applies. The description correctly frames the call as taking no selectors by emphasizing the authenticated actor's own context.

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 ('identifying'/'Reads') and specific resource (the authenticated actor's account label, organization, role, permitted modules). It is clearly distinguishable from get_organization and list_organization_users because it scopes to the calling actor rather than an arbitrary org or user roster.

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 ('Use this when identifying which RetailHardHat account and organization are connected') and an explicit exclusion ('Do not use to enumerate users or change account permissions'), which routes the agent away from list_organization_users and the permission-mutation tools.

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