jev_catalog_refresh

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

Beyond the annotations, the description discloses atomic refresh behavior, snapshot retention on failure, untrusted external descriptions, and no automatic cloud transfer. These are meaningful behavioral traits an agent needs to know before invoking.

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?

Three sentences deliver distinct value: purpose and safety bound, prerequisite and failure atomicity, and trust/cloud behavior. The description is front-loaded and contains no filler.

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?

With no parameters, an output schema present, and annotations covering safety, the description covers prerequisites, failure behavior, and data trust boundaries. Nothing needed to invoke the tool correctly is missing.

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?

There are zero parameters and the input schema is the empty object, so the description has no parameter semantics to add. Baseline 4 applies because there is no parameter gap for the description to compensate for.

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 action, 'Discover tools/schemas', and a specific resource, 'explicitly configured loopback MCP servers'. It also adds a negative constraint, 'no tools execute', which differentiates it from execution-focused sibling 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?

It provides a clear prerequisite: 'Configure JEV_CATALOG_FILE first', and the phrase 'explicitly configured loopback MCP servers' gives context for when this refresh tool is applicable. However, it does not explicitly name alternatives or state when not to use it.

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