get_MIE_file

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

Discloses return format (YAML string or error with valid names) and the necessity to call before SPARQL. No annotations exist, but the description adequately covers key behaviors. Could mention read-only nature or caching, but not required.

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?

Concise with an imperative front-load. All information is relevant. Slightly redundant emphasis, but overall efficient.

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?

Provides necessary context for a simple retrieval tool: the tool must be used first, returns YAML or error. Output schema likely defines return structure, so description does not need to elaborate further.

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%, so parameters are well-described. The tool description adds value by explaining that 'database' must be exactly one of the listed names and warns against using endpoint group names, which is not in the 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 identifies the tool's function: retrieving the MIE file for a database. The description explicitly states it is a prerequisite for SPARQL queries, distinguishing from sibling search and query tools.

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 explicit step-by-step usage instructions: 'At the start of any task, identify ALL databases needed and call this tool for EACH of them before writing any SPARQL queries.' Also warns against misuse (passing endpoint group names) and describes error behavior.

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