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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new context: only *published* OOS are returned and results include org metadata. It does not cover pagination behavior beyond what the schema states, but the added scope information is meaningful.

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?

Three short sentences, front-loaded with the resource and scope, followed by filters and return shape. No filler.

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 6-parameter, zero-required, read-only browse tool with annotations and no output schema, the description covers scope, filters, and return contents adequately. Pagination/sort defaults are left to the schema, which is acceptable.

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%, so the baseline is 3; the description only restates the filterable dimensions already documented in the schema. It also says 'filter by ... quality tier', while the schema exposes quality only as a sort enum, not a filter — a minor mismatch that adds no clarity.

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 ('Browse') and resource ('published Organizational Operating Systems on OTP'), and the 'published' scope implicitly separates it from get_oos and publish_oos. It never names those siblings explicitly, so an agent must infer the distinction.

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 listing of filters implies a discovery/browsing use case, and the word 'published' implies read-only discovery of others' OOS. There is no explicit when-to-use/when-not statement and no named alternative (e.g. 'use get_oos for a single OOS you already know').

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