Add generic health record

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

Annotations indicate this is a mutable operation (readOnlyHint=false). The description adds 'store', which aligns but does not disclose any additional behavioral traits such as authorization needs, side effects, or rate limits. It is adequate but not enhanced.

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 single, short sentence, which is concise but sacrifices necessary detail about parameters and behavior. It is not optimally structured for quick comprehension of all essential aspects.

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?

Given the tool has 8 parameters, 2 required, and an output schema (not shown), the description is incomplete. It does not mention what the tool returns or provide any context beyond its catch-all purpose. The sibling list helps, but the description itself is insufficient.

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 input schema has 8 parameters with 0% description coverage. The description fails to explain any parameter meaning, such as record_type, title, body, or extra_json. This is a critical gap for an AI agent to correctly invoke the tool.

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 action (store) and the resource (health datum that does not fit a dedicated table). It distinguishes from the many sibling tools by indicating it is a catch-all for generic health data.

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 description provides clear guidance on when to use this tool: for health data that does not have a dedicated table. It implies not to use it when a specific tool exists, though it does not explicitly list alternatives.

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