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

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds workflow context by marking it as '[Step 1 of explore_information · optional]' and lists the information returned, which helps an agent understand what a successful call provides.

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 front-loaded with workflow context, then a compact summary of coverage, usage guidance, and an example. Every sentence adds useful information for selection and invocation without unnecessary 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?

For a zero-parameter, read-only overview tool with no output schema, the description sufficiently enumerates what the response covers, so an agent knows what it will get. Annotations and the empty schema cover the rest, making the definition complete for its complexity.

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 the schema is empty, so there are no parameter semantics to explain. The example call get_emora_overview({}) reinforces that no arguments are required. The baseline for a zero-parameter tool is 4.

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 gives a specific verb ('Describes') and resource ('Emora Health'), then enumerates the covered areas: services, states served, insurance accepted, ages seen, how care works, and care team contact. This clearly distinguishes it from task-specific siblings like get_availability, get_cost_estimate, and search_providers.

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 provides an explicit 'Use when' clause covering parent questions about what Emora is, what it offers, where it works, and which plans it accepts. It lacks when-not guidance or named alternatives, but the usage context is clear.

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