whodb_platform_package_library

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered. The description adds the fact that workspace targeting is per-call and does not mutate session defaults, which is useful context, but it says nothing about result size, pagination, or how the two package sources are combined.

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 short, front-loaded sentences with no filler; the purpose leads and the targeting caveat follows. The second sentence partially duplicates the workspace schema description, which is the only minor redundancy.

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?

No output schema exists, but the tool is read-only, takes no required parameters, and all four parameters are fully documented in the schema, so an agent can invoke it correctly. The remaining gap is sibling disambiguation across the many package-related tools, which the description never addresses.

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%, including detailed nested workspace docs ('Omit to use the session default set by whodb_platform_session_use...'), and the description's second sentence largely restates that. A 3 baseline is appropriate since the schema, not the description, carries parameter meaning.

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 and resource ('Search packages shared with the organization or available through the package library'), so the agent knows it is a read/search operation over packages. However, it does not distinguish itself from close siblings like whodb_platform_packages, whodb_platform_package, or whodb_platform_shared_package, and the 'or' phrasing leaves the scope of the result set slightly ambiguous.

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 only usage guidance is about the workspace parameter ('per-call targeting without changing defaults'), which implicitly suggests preferring whodb_platform_session_use for persistent defaults. There is no statement of when to pick this tool over whodb_platform_packages or whodb_platform_shared_package, and no exclusions or prerequisites.

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