get_pregnancy_summary

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — it does not say what period the summary covers, what data source or permissions it needs, or whether it returns nothing when tracking is uninitialized.

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?

It is a single short fragment with no filler, so nothing is wasted — but the fragment is so minimal that it barely earns its place, and there is no front-loaded scoping or content detail to structure.

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 tool with no output schema, the description is the only place an agent could learn what the summary contains or over what window. It supplies none of that, leaving the agent unable to predict the response shape.

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 takes zero parameters, so per the rubric the baseline is 4. There is no parameter information the description could usefully supply, and the empty schema is self-explanatory.

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 is effectively a restatement of the tool name: 'get_pregnancy_summary' → 'The pregnancy-tracking summary.' It identifies the resource domain but adds no verb, scope, or distinguishing detail, and does nothing to separate it from the many sibling summaries (get_menstrual_cycle_summary, get_golf_summary, get_user_summary, get_progress_summary_between_dates).

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?

There is no when-to-use guidance, no prerequisites, and no named alternative among the numerous summary siblings. An agent has no signal about when this tool is the right choice versus get_menstrual_cycle_summary or the other pregnancy/menstrual tools.

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