citation_report

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool writes a file to disk, uses a default path of exports/{camp_id}.cit.md when path is omitted, and returns the path and size. It could additionally note overwrite behavior or permission requirements, but it provides substantial behavioral context beyond basic invocation.

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 compact and well-structured, front-loading the core outcome and then organizing usage guidance into WHEN and NOT WHEN blocks. Every sentence adds useful information, and the alternative tool is named clearly.

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 simple two-parameter tool with no annotations, the description covers purpose, output location, return value, and when not to use it. It is slightly incomplete on camp_id semantics and path format, but the presence of an output schema and the clear sibling routing make it sufficient for correct invocation.

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%, so the description must compensate. It does explain the path parameter by giving a default path behavior, and camp_id appears in that default path, implying it is the campaign identifier. However, camp_id itself is not explicitly described, and it is unclear whether path should be a directory, a full file path, or a filename.

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 produces a cited report as a ready-made Markdown file with verified source excerpts, numbering, and a references section. It also explicitly distinguishes itself from citation_pack, so an agent can select it correctly without opening schemas.

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 uses explicit WHEN and NOT WHEN sections, stating that this tool is for when a ready cited document file is needed to attach/send/save, and explicitly says to use citation_pack when text is needed for synthesis. This is model guidance for choosing between siblings.

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