rlm_svg_bundle_ingest

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

Describes dry_run behavior and metadata storage, but lacks details on side effects, bundle generation specifics, and behavior of other parameters like reindex. No annotations to supplement.

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-sentence description is highly concise with front-loaded purpose and key usage hint. Every sentence adds value.

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?

Given 7 parameters, no output schema, and no annotations, the description covers dry_run and metadata but omits behavior of include_enriched_svg, reindex modes, and bundle structure. Moderate completeness.

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 100%, and description adds context on dry_run and metadata, but does not elaborate on remaining parameters beyond schema 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?

The description clearly states the tool generates an SVG companion context bundle and optionally uploads Markdown documents. It distinguishes from sibling tools as none explicitly handle SVG bundle ingestion.

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?

Provides guidance on using dry_run=true to preview bundles, but lacks explicit when not to use or alternatives. Context suggests this is a specialized tool without direct siblings.

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