github_packages_get_package_for_organization

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

No annotations provided, and the description gives no behavioral details such as whether the call is read-only, error conditions, authentication requirements, or response format. The agent is left with no insight beyond the tool name.

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 one-sentence description is front-loaded and minimal, but it is too sparse to be useful. It is concise but at the expense of necessary detail.

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 or return value explanation. The description fails to indicate what data is returned or any important constraints. For a tool fetching a package, this is severely incomplete.

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?

While schema coverage is 100%, each parameter description is merely the parameter name (e.g., 'org', 'package_type'), adding no meaning. The tool description does not elaborate on these parameters or their values, so the agent gains no additional understanding.

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 states a clear action 'Get a package' for a specific scope 'organization', distinguishing it from user-focused variants. However, it lacks specificity about the type of package (e.g., container, npm) and does not differentiate from other get_package tools for org.

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?

No guidance on when to use this tool versus other package-related tools like delete, list, or get versions. No exclusions or context provided.

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