save_feature_review

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

With no annotations, the description carries full burden and only discloses that data is saved and optionally exported to Obsidian. It omits important behavioral details: whether export overwrites or creates notes, whether the operation is idempotent, any prerequisites for Obsidian export, or whether saving affects other project state. The optional-export behavior is a useful hint but not enough for a mutation/export tool.

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 one short sentence that front-loads the core action. It contains no redundant filler beyond the '[MCP Tool]' prefix. It is appropriately concise for the amount of meaning it conveys, though it sacrifices helpful detail.

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?

This is a complex tool with 9 parameters (7 required), a nested object, an optional export side-effect, and no output schema or annotations. The one-line description is grossly insufficient: it leaves parameter semantics, side effects, return behavior, prerequisites, and relationship to sibling lifecycle tools entirely unexplained.

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 parameter-level meaning. It says the tool saves 'review data' but does not clarify the ownership object structure, the expected format of code_flow, the meaning of alternatives vs. weaknesses, or what verified and export_to_obsidian control. The description fails to compensate for the schema's lack of descriptions.

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 names a specific action ('saves learning retrospective/review data') and a clear context ('after feature implementation is complete'), plus an optional secondary action ('export to Obsidian Vault'). It is clear and informative, though it does not explicitly differentiate itself from siblings like record_decision or record_debug_attempt beyond the inherent difference in the resource.

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 a temporal condition for use: after feature implementation is complete. This implies the tool belongs at the end of the feature lifecycle. However, it does not mention alternatives, exclusion criteria, or how this relates to finish_feature or record_decision, leaving some routing ambiguity.

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