mempalace_check_duplicate

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

Without annotations, the description bears full burden for behavioral disclosure. It fails to state whether this is a read-only operation, what it returns (e.g., boolean, list), or any side effects. The threshold parameter's impact is not explained beyond the schema.

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, well-constructed sentence that conveys the core purpose efficiently with no redundant information.

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 simple tool lacks output specification, leaving the agent unaware of what the result looks like (e.g., boolean or list of similar content). The domain term 'palace' is not explained, coupling with sibling tools but without context for new users.

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%, with clear descriptions for both parameters. The tool description adds no extra semantic value beyond what the schema already provides. Baseline score 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 the tool checks for content existence in the palace before filing, using a specific verb and resource. However, it could be more precise by defining 'exists' (exact or similarity match) and distinguishing it from similar search or find tools more explicitly.

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 use 'before filing' but provides no when-not-to-use hints, alternative tool recommendations, or exclusion criteria. Among siblings like mempalace_search and mempalace_find_tunnels, no guidance is given for choosing this tool.

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