get_diagram_image_by_id

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that an image is fetched, without revealing the output format (e.g., base64, URL, binary), error handling, or any side effects. This is a minimal disclosure that leaves significant ambiguity for the agent.

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 a single sentence that immediately conveys the tool's purpose and scope, with no redundant or vague wording. It is front-loaded and every word earns its place.

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?

The tool is simple with one parameter, but the absence of an output schema and annotations means the description must clarify the return format, which it does not. The agent is left uncertain about how to consume the 'image' result. However, given the simplicity of a read-only getter, the description is minimally adequate.

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?

The input schema covers 100% of parameters, with a detailed description for diagramId that adds practical value by referencing get_all_diagrams_info. The description itself adds no additional parameter semantics, but the schema's cross-tool guidance elevates it above the baseline of 3.

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 verb 'Get' and the specific resource ('image of a diagram by its ID') in StarUML. It distinguishes itself from sibling tools like get_all_diagrams_info and get_current_diagram_info, which return metadata rather than the image.

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 does not explicitly state when to use this tool versus alternatives, but the schema parameter description hints at the workflow by directing users to get_all_diagrams_info for the diagramId. No exclusions or alternative usage guidance are provided, leaving the usage context implied rather than explicit.

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