更新本地健康档案

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

The description indicates mutation (create/update) but does not disclose behavioral details such as whether it overwrites or merges fields, authentication requirements, side effects, or constraints. With no annotations, these gaps are significant.

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 brief (one sentence) and concise, but it sacrifices necessary detail. It is not structured to aid an agent in understanding tool usage efficiently.

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 8 parameters with no descriptions, no output schema, and no annotations, the description is grossly insufficient. It does not cover return values, error handling, or data persistence behavior.

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 provides no explanation of the 8 parameters (e.g., format for riskFactors, expected values). The agent receives no semantic help beyond the raw schema.

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 'Create or update MCP server-side single patient health profile,' which clearly identifies the verb and resource. However, it does not differentiate between creation and update scenarios, and sibling tools like health_profile_get and health_medication_add exist but are not distinguished.

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 provided on when to use this tool versus alternatives such as health_profile_get (for reading) or health_medication_add (for specific conditions). The description lacks context for appropriate usage.

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