jev_catalog_get

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context by stating the tool executes nothing and only retrieves a discovered schema. It also explains the version-check behavior, which goes beyond what annotations provide. No contradiction exists.

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 with no filler: the core action is front-loaded, and the concurrency guard and execution boundary are each purposeful. Every sentence adds information an agent needs.

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 read-only annotations and an output schema, the description is largely complete: it identifies the target, explains the version parameter, and explicitly warns against using this tool for execution. The only minor gap is that 'action preset' is mentioned but not elaborated, though the output schema likely covers that.

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 carries the burden for parameter meaning. It clearly explains that version is the value returned by search and is used to reject a changed catalog. tool_id is not formally defined, but its role as the catalog identifier is reasonably inferable from 'one exact discovered tool 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?

The description states a specific operation: retrieving one exact discovered tool schema and any action preset, and explicitly says it 'executes nothing.' This clearly distinguishes it from catalog search/refresh tools and from sibling execution tools like unreal_workflow_apply.

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 tells the agent to pass the version returned by search to reject a changed catalog, and directs authorized execution to the external server's own client instead of this tool. It gives clear context and a concrete alternative, though it does not explicitly enumerate exclusions versus jev_catalog_search or jev_catalog_refresh.

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