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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable context about the public-only boundary, explicitly listing excluded data types (phone numbers, addresses, staff contacts, applicant records) and the shape of heroStories. No contradiction with annotations.

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?

The description is three sentences: the first front-loads what is returned and why, the second covers when to use it, and the third sets boundaries. Every sentence earns its place with no filler or redundancy.

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 parameters Morphic, an output schema present, and annotations already covering safety, the description still adds the key selection triggers, the public-only guarantee, and story fields. Nothing needed to invoke this zero-input read tool correctly is missing.

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 has zero parameters and an empty input schema, so there is no parameter burden for the description to carry. The description reinforces this with 'Requires no input', which is sufficient.

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 ('Retrieve') and resource ('public organization profile of VA Heroes PH'), with a detailed list of fields and hero stories. It clearly distinguishes this tool from program/FAQ/hero-path siblings by its focus on organization-level public information.

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 gives explicit trigger scenarios ('when a visitor asks who VA Heroes PH is, what it does, whether it is credible, where to follow it, or where to apply') and states what it does not return. It does not explicitly name sibling tools as alternatives, but the usage context is otherwise clear and actionable.

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