ae_list_blender_jobs

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

There are no annotations, so the description carries the burden of behavioral disclosure. It reveals that the tool reads from a local directory (~/.ae-mcp/blender-exchange/) and 'List' implies a read-only operation, but it does not explicitly state side-effect-free behavior or what happens if the directory is missing.

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?

One sentence, no filler, and the most important scoping information (what is listed and where) is front-loaded. 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?

With zero parameters and no output schema, the description is mostly sufficient: it states the source location and the resource type. It does not describe the return structure, but for a simple list tool this is a minor gap.

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?

The input schema has no properties, so there are no parameters needing semantic explanation. The description adds no parameter detail because none exists, which is appropriate.

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 uses a specific verb ('List') and a specific resource ('Blender→AE exchange jobs'), and pins the scope to a concrete filesystem path. This clearly distinguishes it from sibling tools like ae_list_instances or ae_list_compositions.

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 location and resource are explicit, making it clear this tool is for listing Blender exchange jobs from a local directory. It does not list explicit exclusions or alternatives, but the domain-specific naming and path are sufficient contextual guidance.

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