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

Beyond the readOnlyHint=false / destructiveHint=false annotations, the description discloses meaningful behavior: the operation is atomic, an idempotency_key makes retries safe, the server infers category and position, the new post is appended as the last trail step, and contributor output becomes a draft for review. This adds real context the annotations do not carry.

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 front-loaded with the core atomic action, then moves to procedural guidance, with no filler sentences. It is compact for the amount of behavior it conveys, though the sentence flow is a bit clipped.

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?

An output schema exists and annotations cover the safety profile, so the description needn't explain return values or mutation risk. It covers the workflow, draft state, idempotency, and server-side inference; the remaining gap is that several of the 10 undocumented parameters are never given semantics.

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% across 10 parameters, so the description must compensate. It explains the important semantics of related_topics (existing topic IDs placed in learning order, appended last) and idempotency_key, and implies category_topic_id is optional via server-side inference, but leaves map_id, language, trail_title, trail_summary, title, summary, and content unaddressed.

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 action (atomically add a study text, related links, and an ordered learning trail) and a clear resource, and it distinguishes itself from siblings by naming find_related_map_topics as a prerequisite. The phrasing is slightly muddled in places (study text vs. trail vs. post), but an agent can identify the operation and its scope.

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?

It gives an explicit prerequisite and ordering instruction ('First call find_related_map_topics') and notes that contributors produce drafts for review. It does not state when-not to use this versus siblings like add_map_content or create_topic_at_position, so it stops short of full routing guidance.

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