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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: an authentication requirement and the fact that one sign-in can chart several people (multi-profile behavior), which the annotations do not convey.

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 dense colon-list sentence, but it is front-loaded with the auth prerequisite and every clause describes a distinct returned field rather than padding. Slightly run-on, though no sentence is wasted.

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 does the heavy lifting by enumerating the returned data (ids, weigh-ins in pounds and trend, treatment plan fields, side effects with ids, reminders, reward). It is close to sufficient for an agent to consume the result, missing only detail on formats such as how 'the trend' is represented.

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 the baseline is 4. The description appropriately spends no space on parameter syntax and instead documents the shape of what comes back.

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 makes clear this returns the signed-in user's health profiles and enumerates their contents (weigh-ins, treatment plan, side effects, reminders), which distinguishes it from siblings like get_my_account and get_lab_results. It never states a clean verb+resource summary sentence, but the resource and scope are unambiguous from the enumeration.

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 states a prerequisite ('Requires signing in with a Deer account') and hints at downstream use by noting the profile id is 'needed to log anything', which implies this is the lookup step before log_weight or report_side_effect. However, it never explicitly says when to call this versus get_my_account or get_lab_results, leaving routing to inference.

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