render_report

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

Describes image embedding, linking, whitespace stripping, output path behavior, and return dict. Annotations absent, so description carries full burden and does it well.

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?

Well-structured with headings and lists, informative yet not verbose. Could be slightly more concise, but clarity is high.

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?

Covers all parameter behavior, optionality, output schema, and usage expectations. No gaps given the tool's complexity.

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 has 0% description coverage; description provides detailed explanations for all 4 parameters, including roles, formats, and defaults.

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 clearly it assembles a Markdown executive report from prose findings and artifact links. Distinguishes from siblings which are about abstraction, discovery, filtering, etc.

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?

Advises to pass findings after calling abstract_*/get_* tools, giving clear context. Does not explicitly list when not to use, but siblings provide alternative contexts.

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