list_factory_device_profiles

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be a safe read operation. The description adds minimal behavioral context: 'producer-oriented' hints at audience, but it doesn't mention whether it returns cached/static data, whether it requires network, or any performance implications. Given the annotations, a 3 is appropriate.

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 a single, succinct sentence that front-loads the primary purpose. No unnecessary words; it is appropriately sized for a low-complexity tool with no parameters.

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 zero-parameter list tool with strong annotations and a clear purpose, the description is nearly complete. It could mention what type of information the profiles contain (e.g., parameter names, macros) or whether it includes third-party devices, but that 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 tool has zero parameters, so the schema is empty and there is nothing to explain. The description's mention of 'producer-oriented' and 'foundational' gives some semantic context about what will be returned, but since there are no parameters, the description's role is minimal. Baseline 4 for no params is correct.

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 function: listing producer-oriented knowledge profiles for foundational Ableton factory devices. It uses a specific verb and resource, and the scope ('foundational', 'producer-oriented') helps differentiate from generic list tools. However, it doesn't explicitly name any sibling tool to contrast with.

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 implies when to use it (when you need knowledge profiles for factory devices) but provides no explicit guidance on when not to use it or what alternatives exist. Siblings like 'get_factory_device_context' or 'get_factory_browser_items' might overlap, but this isn't addressed.

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