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

Annotations declare a mutating, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds the useful behavioral detail that expectedSpecVersion guards against stale writes, but says nothing about what happens on a version mismatch, required permissions, or what state is changed.

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?

Two short sentences with no filler, and the core purpose is front-loaded ahead of the concurrency caveat. Efficient, though the second sentence could be phrased more fully.

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?

For a mutating tool with a nested config object and no output schema, the description covers the essentials of what it does and the optimistic-concurrency requirement. It omits what the search config comprises (nested schema does cover this) and the failure behavior on a stale version, leaving a real gap.

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?

Top-level schema description coverage is 0%: projectId, expectedSpecVersion, and the input object have no schema descriptions. The description compensates for expectedSpecVersion only, leaving projectId and input unexplained at the top level.

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 states a specific verb and resource ('Configure how search behaves in a project map'), which is enough to distinguish it from sibling config tools like configure_popup and configure_legend. It does not explicitly name those siblings, but the search-specific scope is clear.

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?

There is no when-to-use guidance and no alternatives are named. The only contextual hint is that expectedSpecVersion prevents stale writes, which is a concurrency note rather than usage guidance for choosing this tool over siblings.

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