load_model_from_content

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

Disclosures align with destructiveHint: true, stating it 'replaces active model.' Adds safety details (DTD/entity rejection, size limit) beyond annotations. Could mention if undo history is cleared, but overall transparent.

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 Args, Returns, Errors sections. First sentence conveys core purpose. No extraneous text; every sentence adds value. Concise yet comprehensive.

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 input constraints, output format (success envelope with model_info), errors, and alternative tool guidance. Having an output schema further supports completeness. No gaps identified.

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?

With 0% schema coverage, description fully explains both parameters: model_content constraints (starts with `<`, ≤10 MiB, safety rejections) and content_format enum values and defaults. Adds significant meaning beyond 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?

Clearly states 'Load an ArchiMate model from XML string content (replaces active model)', specifying verb, resource, and source. Distinguishes from sibling 'load_model_from_file' by noting it expects XML payload, not path.

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 advises when to use alternatives: 'For loading large files or paths use load_model_from_file instead; this tool expects the actual XML payload, not a path.' Also includes constraints like size limit and safety rejections.

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