get_MIE_file

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

Despite no annotations, the description covers the tool's purpose and content (schema, examples). It does not discuss error handling or output format, but the core read-only behavior is clear.

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 front-loaded with a bold critical instruction, followed by a concise purpose statement. While clear, it could be slightly more streamlined without losing key guidance.

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 the output schema exists, the description adequately covers usage context and return content (ShEx schema, examples). It does not detail output structure but is sufficient for typical use.

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 33% schema description coverage, the description fails to clarify which parameter (db, dbname, or database) should be used or how they relate. The description only implies passing database names but does not resolve parameter ambiguity.

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 retrieves the MIE file containing ShEx schema, RDF, and SPARQL examples for a specific RDF database. It distinguishes itself from sibling tools by focusing on this metadata prerequisite.

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 explicitly instructs to call this tool for each needed database before writing any SPARQL queries, providing a clear prerequisite. This contrasts with sibling tools like run_sparql, which should be used after this tool.

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