get_plugin_install_package

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

No annotations provided, so description carries full burden. It describes return fields (content_full, install_targets, plugin_tracking) and their usage details. Does not cover auth or side effects, but for a read-like tool the output description is thorough.

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 well-structured with bullet points and front-loaded purpose. It is fairly long but each sentence adds value. Could be slightly tighter but overall efficient for the information conveyed.

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 one parameter, no annotations, and presence of output schema, the description provides sufficient context: what the tool returns and how to interpret it. It lacks error handling or prerequisites, but is largely complete for its simplicity.

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 0% for the single parameter 'plugin'. The description does not elaborate on its format or constraints beyond the tool context. It relies on the parameter name and tool purpose to convey 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?

The description explicitly states the tool's purpose: 'Get full documentation AND install-ready files for an entire plugin in one call.' It distinguishes from siblings like get_entry by noting this is for full plugins vs individual entries.

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?

Provides clear when-to-use scenarios: 'install a plugin... get the documentation and install files... know where to place artefacts.' Also explicitly suggests preferring this over multiple get_entry calls, offering an alternative.

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