get_package_knowledge

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and external-lookup behavior are covered structurally. The description adds only that multiple sources are merged, and says nothing about what happens when a package lacks an AGENTS.md, when Context7 has no match, or how partial results are surfaced.

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?

A single short sentence is efficient and front-loaded, but here brevity comes at the cost of under-specification rather than sharpness — there is no wasted clause, yet also no sentence that establishes what the agent gets back or how to choose inputs.

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?

Although an output schema exists (so return shape needn't be described), a 5-parameter aggregation tool spanning three external sources needs far more than one sentence. Nothing addresses repository/bioconductor selection, revision pinning, answerable-question semantics, or the behavior of combining sources.

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 0% across 5 parameters, so the description carries the full burden and fails: it never explains what 'package', 'revision', 'repository', 'bioc_version', or especially 'question' mean or how they change behavior. 'Requested AGENTS.md and Context7 material' vaguely gestures at optional inputs but does not map to any parameter.

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 verb 'combine' plus the resources (package metadata, AGENTS.md, Context7 material) hints that this is an aggregator over package info, agent guidance, and external docs. However, it never states that explicitly, and with siblings like get_package_info, get_package_agent_guidance, and get_context7_docs present, an agent cannot tell from the text whether this replaces those tools or supplements them.

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?

There is no when-to-use guidance, no mention of alternatives, and no conditions under which an agent should pick this over the three single-purpose siblings it apparently wraps. The word 'requested' implies optionality but gives no criteria.

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