get_r_prompt_context

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that resolution includes direct dependencies and source provenance, which is real content beyond the annotations, but says nothing about network resolution behavior, failure modes, or how versions are chosen.

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 front-loaded sentence with no filler. Efficient, though its brevity is achieved partly by omitting needed detail rather than by sharp editing.

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?

With an output schema present, return values needn't be described, and annotations cover safety. However, three undocumented parameters and no usage boundaries against a dense sibling set leave the definition under-specified for what appears to be a context-assembly tool.

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%, so the description carries the full burden. It loosely implies the 'packages' parameter ('selected R package versions') but never explains r_version or bioconductor_release, or the accepted package string format.

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 'Resolve' with the objects 'R package versions, direct dependencies and source provenance' gives a rough sense of the operation. But the tool name implies prompt-context assembly, which the description never mentions, and there is no differentiation from siblings like get_dependencies or check_package_version that appear to cover overlapping ground.

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 statement of when to use this tool versus the many adjacent siblings (get_package_info, get_dependencies, check_package_version, check_package_compatibility). The agent is left to infer the selection condition entirely.

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