load_sources

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

No annotations provided; description only says 'Load', with no disclosure of whether sources are appended/replaced, error handling, required permissions, or side effects. Needs more behavioral context.

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?

Extremely concise: two sentences with no filler. Every word is purposeful. Ideal length for a simple tool.

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 loading operation with array parameter, description lacks critical details: append vs replace behavior, response information (output schema exists but unused), and handling of invalid paths. Incomplete despite tool's moderate 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 coverage 0% (no schema descriptions). Description adds minimal meaning: 'List of paths to media files'. Does not specify format, supported URIs, or constraints. Partial improvement over bare schema.

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?

Description explicitly states it loads multiple media files into RV, with a clear verb ('Load') and resource. Differentiates from sibling 'load_source' (singular) by indicating batch operation ('at once').

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?

Implied usage: use for multiple files vs single via sibling 'load_source'. Lacks explicit when-not or alternative guidance, but is sufficient given tool naming and description.

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