whodb_platform_org_package_installations

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds the default-inheritance behavior of workspace targeting beyond what annotations provide, but says nothing about return shape or pagination for what is presumably a potentially large listing.

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?

Two front-loaded sentences that establish scope first and the targeting mechanic second, with no filler. Slightly compressed phrasing ('optionally for one package') costs a little clarity but the structure is efficient.

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 read-only listing tool whose annotations and full schema coverage carry most of the burden, this is adequate. The notable remaining gap is disambiguation from whodb_platform_package_installations and the absence of any note on result volume or ordering.

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 every parameter is already documented in the schema and the baseline is 3. The description adds only that id may scope to a single package; it does not clarify fields, search, or how the nested workspace object interacts beyond restating the schema.

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 (List) and resource (package installations) scoped to the selected organization, with an optional single-package filter. However, it does not distinguish itself from the near-identically named sibling whodb_platform_package_installations, so an agent cannot tell from the description alone which of the two to pick.

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?

Explains the per-call workspace targeting mechanic (omit to fall back to session default) and points at discovery tools, which is useful operational context. It stops short of when-to-use guidance against the sibling tools that overlap in scope, and gives no explicit exclusions.

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