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

Adds real context beyond annotations: unknown keys are rejected, nesting is capped at one level, and it returns {recordId} usable by muninn_memory_get/update. Annotations already cover the mutation/safety profile (readOnlyHint=false, idempotentHint=false), so this is solid added value, though it doesn't detail failure modes or permissions.

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?

Three dense sentences that front-load the core action, then conditional nesting guidance, then the return value. No wasted prose.

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?

No output schema, but the description explicitly states the return shape ({recordId}). Combined with nesting rules and key-validation behavior, an agent has everything needed to call this correctly.

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 coverage is 100%, so baseline is 3, but the description adds meaning: `values` is keyed by field key, and parentRecordId carries the nested-table semantics. This clarifies how parameters interact 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?

Specific verb 'Add' + resource 'record to a table', clearly distinct from siblings like muninn_table_define (schema creation) and muninn_table_records_list (reading). An agent can immediately tell what this does without opening the schema.

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?

Points the agent to muninn_table_list for field keys and explains the parentRecordId condition for filing nested log entries under a standing record. It gives clear usage context but stops short of explicit when-not-to-use guidance or naming a closest alternative to compare against.

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