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

Annotations already mark the tool as read-only, idempotent, and non-destructive; the description adds valuable context beyond that by stating it requires no input, returning only a predefined overview shape. It also explicitly excludes pricing, class schedules, enrolment status, batch dates, and applicant data, and clarifies that no separate course catalogue exists, which prevents false expectations.

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?

Every sentence earns its place: purpose, when to use, no-input requirement, return shape, and explicit non-scope. The most important selection information is front-loaded before the negative contract, and there is no 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?

For a zero-input, read-only overview tool with sibling distinctions, the description covers purpose, usage, return structure, and limitations. Nothing an agent needs to decide when to call it is missing, and the output schema provides the detailed return formatting.

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?

There are zero parameters, and the empty schema already implies no input; the description makes this explicit with 'Requires no input,' which is exactly the guidance an agent needs for a parameterless tool. The 0-parameter baseline is 4, and the explicit statement raises it to 5.

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 opens with a specific verb and resource: 'Retrieve a single structured overview of how the VA Heroes PH program works,' then enumerates exactly what that overview contains: Hero Paths, the sales/Loan Officer path, impact stats, and the application page. It also distinguishes itself from specific-track tools with 'instead of asking about one specific track.'

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?

It gives clear when-to-use context ('Use it when a visitor asks broadly what VA Heroes PH offers, how the training works, or how to get started') and an explicit when-not ('instead of asking about one specific track'). However, it does not explicitly name the alternative sibling tools, so the agent has to infer them from the sibling list.

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