get_organization

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds no behavioral context beyond what annotations provide—no mention of 404 behavior, response format, or that it returns a single object. With annotations covering the safety profile, a 3 is appropriate.

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?

A single sentence with zero waste. The key information—what the tool does and how it identifies the resource—is front-loaded and immediately actionable.

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 simple single-resource read tool with one parameter and annotations covering safety, the description is nearly complete. It doesn't explain return values, but no output schema exists and the tool's purpose makes the return type predictable. The only minor gap is not explicitly routing to list_organizations for multi-fetch scenarios.

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?

Schema description coverage is 100%—the only parameter 'id' is described as 'Organization ID' in the schema. The description adds no additional meaning beyond restating that the organization is fetched by ID. Baseline 3 is correct 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?

The description 'Get a specific organization by ID' clearly states the verb (get), resource (organization), and the identifying parameter (ID). It distinguishes from list_organizations (which lists all) and create/update/delete_organization siblings, though it doesn't explicitly name them.

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 implies usage: use when you need a single organization by its ID. It doesn't explicitly state when not to use it or mention alternatives like list_organizations for fetching multiple organizations, but the context is reasonably clear given the sibling tool names.

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