engine_static_load

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that this is a read-only operation ('load', 'read before editing') and warns about the save overwrite behavior. However, it does not mention error handling, return format, or side effects beyond reading. This is a moderate level of transparency for a simple load tool.

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?

Two short sentences, front-loaded with the primary purpose and immediately followed by a crucial usage note. There is zero fluff; 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?

For a simple one-parameter load tool with no output schema, the description covers the essentials: what it loads, where, and when to use it. It omits explicit return format (likely file content), but that is reasonably inferred. It lacks mention of error cases, but these are minor for a basic read operation.

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 description coverage is 0%, so the description must compensate. It provides a concrete path pattern ('templates/<t>/statics/...') that gives the agent a clear template for the 'path' parameter, adding significant meaning beyond the bare schema. It doesn't specify relative vs. absolute or file extensions, but the convention is enough for correct usage.

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 states a specific verb ('load') and a well-defined resource ('static file, css or js') with a path convention ('templates/<t>/statics/...'). This clearly distinguishes it from sibling load tools like engine_image_load (images), engine_html_load (HTML), and engine_files_load (other files). The 'Read before editing' note further clarifies its role as a read operation.

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 gives clear context: it is for reading css/js static files, and the instruction 'Read before editing - save overwrites' signals when to use it (before a save operation) and implies the counterpart save tool exists. It doesn't explicitly list alternatives or exclusions, but the specificity of the resource type and the naming of siblings make the intended use unambiguous.

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