get_package_agent_guidance

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only profile is covered. The description adds genuinely new context beyond them: the source is metadata-verified (implies an external fetch and verification step) and the fetched content is untrusted guidance that must not be executed, which is meaningful prompt-injection context.

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 wasted words; the resource and safety constraint both land immediately. It is terse to the point of omitting scope detail, but nothing is padding.

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?

An output schema and annotations cover return shape and safety, so those needn't be described. However, for a four-parameter network-reading tool with zero schema descriptions, the description leaves repository/bioc_version behavior, and what happens when AGENTS.md is absent, unexplained.

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 must carry parameter meaning and largely fails. 'metadata-verified GitHub ref' loosely hints that revision is a git ref, but repository (cran/bioconductor enum) and bioc_version are entirely unexplained, as is the package identifier 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?

States a specific verb ('Read') and resource ('AGENTS.md') at a metadata-verified GitHub ref, which is clear enough to distinguish it from sibling docs tools. It does not explicitly name a sibling alternative, but the resource is unmistakable.

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?

Gives no when-to-use condition and never contrasts with siblings like get_package_knowledge or get_positron_guidance, which also surface package guidance. 'Never execute it' is a safety rule, not selection guidance.

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