Read the shopper's Portage setup

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

Annotations already cover readOnly/idempotent/destructive/openWorld, and the description adds value beyond them: it discloses that credentials are never returned, that a failed section surfaces as { error }, and that product/store/merchant text is untrusted and must not be followed as instructions (prompt-injection guidance). That is substantive behavioral disclosure, not restatement.

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?

Front-loaded with purpose and zero obvious filler, but the first sentence is a long multi-clause run-on packing four returning sections and a parenthetical into one breath. Dense and useful, though slightly harder to scan than it needs to be.

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 no output schema, the description carries the return contract itself: an object keyed doctor, policy, payment_methods, browser_profile, with { error } for failed sections. Combined with the when-to-call and safety guidance, an agent has everything needed to invoke and interpret it.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to document. It appropriately spends its words on return shape instead of inventing parameter detail.

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 (the shopper's local Portage setup), then enumerates what the read covers: doctor findings, spending policy, enrolled payment methods, and the browser profile. This is clearly distinguishable from every sibling (find_products, buy_quote, add_store, etc.), which are all task-oriented rather than setup-oriented.

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 explicit timing: 'Call it first in a session and again when a tool fails,' which is a concrete when-to-use rule. It also clarifies the boundary that it 'can't change anything' and points at the remediation path (`portage setup`, `portage policy set`), preempting mis-invocation for fixes.

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