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

With no annotations provided, the description carries the full burden. It adds value by listing the exact return fields (id, name, slug, members_count, created_at) and the token cost. It also implies read-only behavior via 'retrieve.' It could be more explicit about side effects, but for a get operation this is sufficient.

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?

The description is four short sentences, each earning its place: purpose, prerequisite/selection, return fields, and cost. It is front-loaded and free of fluff.

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?

Given the presence of an output schema, the description need not explain return values in detail, yet it lists the key fields anyway. It covers the prerequisite, instance selection, and cost, which is complete for a simple get tool. It does not mention error cases, but that is minor.

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 coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema for organization_id, and for clerk_instance_id it essentially restates the schema's guidance ('Pass clerk_instance_id to target a specific connection, or omit it to use the default account' mirrors the parameter description). Thus it stays at baseline.

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 opens with a specific verb+resource: 'Retrieve a single organization from a connected Clerk application.' This clearly distinguishes it from list_organizations (plural) and get_organization_invitation, and the singular 'a single organization' conveys exactly what it does.

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 provides explicit usage guidance: 'Call clerk.get_connected_accounts first' and then explains how to handle clerk_instance_id (pass to target a specific connection, omit for default). It does not explicitly name alternative tools like list_organizations, but the prerequisite and selection logic are clearly stated.

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