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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, but the description adds critical behavioral nuance: AND-combined filters, the minimum token-length rule, refusal behavior, empty-result meaning, and the limitation that service records are not read. This goes well beyond the structured hints and prevents false conclusions about non-presumptive status.

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 dense but every sentence earns its place: use case, output content, input requirement, filtering semantics, empty-result caveat, and service-record limitation. It is front-loaded with the primary use case and contains no filler or repetition.

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 compensates by listing the returned fields: service era, exposure type, required service, legal authority, and evidence needed. It also explains the closed-world limitation on empty results and the boundary of what the tool does not determine (service record matching). This is complete for safe invocation and interpretation.

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% with clear per-parameter examples, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that at least one parameter is required, that filters combine with AND, that condition plus exposureType or serviceEra narrows to their intersection, and the three-character minimum per filter. This enhances the agent's ability to construct valid queries.

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 clearly states both use cases: checking whether a condition is presumptively service connected, and finding presumptive conditions for an exposure or service era. It names the exact resource (presumptive conditions) and includes the specific output fields, distinguishing it from rating/pay/legal-search siblings.

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 opening sentence gives explicit when-to-use guidance tied to veteran questions about presumptive service connection. It also explains required inputs and filtering behavior, though it does not explicitly name alternative tools or when-not-to-use cases. The context is clear enough that an agent can select it appropriately.

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