mempalace_hook_settings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context that this is an adapted tool reporting deployment policy, not actual local settings, which is behavior beyond what annotations convey. There is no contradiction.

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 two sentences, front-loaded with the main purpose, and every clause adds relevant information. It is appropriately sized for a simple read-only query tool.

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 no required parameters, rich annotations, and an output schema, the description is sufficiently complete. It explains the key deployment limitation and the tool's adapted nature, which addresses the main contextual concerns.

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 100% description coverage, with both parameters clearly described. The description itself adds minimal parameter detail, but the schema already explains that silent_save is a requested setting and desktop_toast is not exposed. Baseline of 3 is appropriate.

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 it returns the configured save policy, using a specific verb and resource. It also notes local desktop hook settings are unavailable, which adds useful scoping. However, it does not explicitly distinguish itself from sibling tools like mempalace_status or mempalace_get_drawer.

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 implies this tool is for retrieving the save policy and that local desktop hook settings are not available, giving some context about deployment limitations. It does not explicitly state when to use this tool over alternatives or mention any exclusions, but the 'not available' note partially guides usage.

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