get_pregnancy_summary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'get,' which implies a read operation, but does not disclose any data scope, prerequisites, or behavioral traits beyond that. The description does not contradict annotations because there are none.

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 a short, front-loaded, single sentence with no unnecessary elaboration. It is concise and easy to parse, though it slightly repeats the tool name by adding 'data' without much extra meaning.

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 and an output schema present, the description does not need to explain return values. However, it provides no context about when pregnancy summary data is available or how this tool relates to other health summary tools. The low complexity makes the missing context less damaging, but the description is still minimal.

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, so there is no parameter documentation gap. The schema already fully covers this by having an empty properties object; the description adds nothing about parameters, but none is needed.

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 and resource: 'Get pregnancy summary data.' It is clear what the tool returns at a high level, and 'pregnancy summary' is distinct from most sibling tools. However, it does not explicitly distinguish itself from other summary-style getters.

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?

No guidance is given about when to use this tool versus alternatives. The description is only a bare definition and offers no exclusions, context, or comparison to related tools like get_menstrual_data_for_date or other summary endpoints.

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