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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's 'Read only' merely repeats readOnlyHint; its only added value is telling the agent it returns org identity plus permission/capability information.

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 front-loaded trigger sentence followed by a terse qualifier; it is short and readable. The trailing 'Read only.' is slightly redundant given readOnlyHint=true, which keeps it just under a perfect score.

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 tool with no output schema and annotations covering safety, the description conveys the trigger and the general nature of the result (org identity and permissions). It is nearly complete, lacking only routing guidance relative to its many siblings.

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 baseline is 4; the description has no parameters to clarify and does not need to add any. Nothing is misleading or omitted in this dimension.

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 names a concrete resource (the user's organization) and states what is returned: which org they are in and what actions they may perform. It is a clear read operation, but it does not differentiate itself from siblings like whoami, org_members, or org_activity, which an agent could easily confuse it with.

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?

'Use when the user asks about their organization' gives an implied trigger condition but no explicit when-not guidance and no mention of the crowded org_* alternative space (org_members, org_activity, whoami). An agent must infer which org-related tool applies.

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