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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description earns credit for explaining the mechanism: matching by type+name and panels by title, and re-running updates rather than duplicating. It does not say what happens to existing entries absent from the brief (removal? leave-in-place?), which matters for a destructive import.

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?

Front-loaded with purpose and idempotency before diving into format rules. Dense with nested parentheticals, but nearly every clause carries operational information (inline panels, {{player}}, languages tabs). Slightly overpacked into one paragraph.

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 destructive, idempotent, nested-object import with no output schema, the description covers content authoring rules and duplicate handling well. It leaves out error behavior on malformed formats and the fate of entries omitted from a re-import.

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 only 50% and projectId is undocumented, but the description compensates heavily on the nested 'brief' param: the format string, entries/panels structure, the 'languages' key, and the {{player}} placeholder convention. That is substantive meaning the schema does not provide.

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?

States a specific verb and resource ('Bulk-import a Lunafic Brief') and immediately pins down the payload format ('JSON with format "lunafic-brief/1": entries with panels'). This is clearly distinguishable from the single-entry siblings like create_entry or upsert_panel.

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?

Explicitly says 'Prefer this for whole characters AND player roles', which is real routing guidance against the per-entry siblings. It also gives a non-obvious prerequisite ('supply its panels inline since roles have no default template'). It stops short of naming an explicit when-not-to-use or naming the alternative tool.

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