Search Withings Capabilities

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

Annotations already declare the tool as read-only, idempotent, and non-destructive, so the description has a lighter burden. It adds the 'Use first' behavioral cue but does not describe return values or how the search behaves beyond that, which is adequate but not rich.

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 extremely concise with two short sentences that immediately convey purpose and priority. Every word earns its place, and there is no redundant filler or structured data 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?

The tool is simple, and annotations provide a clear safety profile, but the description lacks details about what the search returns or how to interpret results. Given the openWorldHint and no output schema, a bit more context about the response would improve completeness, but the essential purpose is covered.

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 0%, and the description does not mention the 'query' or 'limit' parameters at all. The parameter names are intuitive, but the description fails to compensate for the lack of schema documentation, leaving their exact semantics underspecified.

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 the tool's purpose with a specific verb ('Find') and resource ('the right Withings tool'), distinguishing it from sibling tools that perform actual data retrieval. The phrase 'Use first' further clarifies its role as a discovery helper.

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 instruction 'Use first' provides explicit guidance on when to invoke this tool, placing it before any other Withings sibling tool. It lacks explicit when-not-to-use or alternative recommendations, but the directive is clear and contextually sufficient for a discovery tool.

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