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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: it returns evidence rows with resolved PubMed and DOI identifiers, implying a lookup/verification behavior rather than a simple list. It doesn't mention pagination or result limits, but for a read-only lookup tool this is a minor gap.

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?

Two sentences with no waste. The trigger condition is front-loaded, the resource is named, and the unique value (PubMed/DOI resolution) is included. Every sentence earns its place.

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?

For a read-only lookup tool with full schema coverage and safety annotations, the description is nearly complete. It explains the purpose, the trigger, and the unique output characteristic. It doesn't describe the exact return shape, but no output schema exists and the description's mention of resolved identifiers gives enough context for an agent to invoke it correctly.

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 100%, so the schema already documents both parameters. The description adds the context that topic and nutrient are used to find evidence rows, but it doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('Call'), a clear resource ('HerStack's evidence rows'), and the purpose: retrieving studies behind a recommendation or claim. It also distinguishes itself from siblings by mentioning resolution to PubMed and DOI identifiers for verification, which is a unique capability.

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?

The description explicitly says when to call ('when the user or you wants the studies behind a recommendation or claim'), which is clear context. It doesn't explicitly name alternatives or exclusions, but the sibling list and the unique verification purpose make the usage context reasonably clear.

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