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

Annotations already establish this is a safe, non-destructive read, so the bar is lower, and the description still adds meaningful context: the profile is the *public* view, consistent with openWorldHint=false, and it enumerates the returned content (OOS files, quality tier, badge, stats), which matters because no output schema exists. It does not state behavior on an unknown or invalid org_id.

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 sentence, front-loaded with the action and resource, followed by the value-bearing content list. No filler, no restating of the title or annotations.

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 single-parameter read tool with no output schema, the description covers the resource, its visibility scope, and the shape of the response. The only meaningful gap is error behavior (org not found / invalid ID), which is minor here.

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?

With a single required parameter at 100% schema coverage, the schema already fully documents org_id including its UUID format and pattern. The description adds nothing beyond 'a specific organization', which is consistent with the baseline of 3 when the schema does the heavy lifting.

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 (get) and resource (organization public profile on OTP) and enumerates what the profile contains: published OOS files, quality tier, badge, stats. It is clearly distinguishable from get_publishers or get_oos, though it does not explicitly contrast itself with those siblings.

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?

Usage is only implied by the verb and the required org_id: look up one org by identifier. There is no explicit when-to-use guidance and no mention of the nearest alternative (get_publishers) or of what to do when the ID is unknown (e.g., list_people / search tools).

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