mem_health

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

The description states the tool is 'deterministic', implying no side effects, but lacks details on error handling, authentication needs, or behavior with invalid project keys. Given no annotations, more disclosure would be beneficial.

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, front-loaded sentence that efficiently conveys the tool's purpose and output without redundant words.

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 description lists report contents (duplicates, contradictions, etc.) but omits output structure, format, and additional context about project keys. For a tool with no output schema and 0% param coverage, more detail is needed for full completeness.

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 explain the 'project_key' parameter beyond its role. No format, constraints, or usage context is provided, leaving the agent to infer meaning.

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 verb 'Return' and the resource 'health report', listing specific contents (duplicates, contradictions, etc.). It distinguishes from sibling tools like mem_health_runtime by specifying 'deterministic' and 'for one project'.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies analysis use but does not differentiate from similar tools like mem_health_runtime or mention alternatives.

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