list_all_body_styles

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

With no annotations, the description carries full burden. It discloses that data is cached for 7 days and that the result is 'raw' (no processing). This adds value beyond the schema. It does not cover auth or rate limits, but for a simple read tool with no parameters, this is adequate.

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, front-loaded sentence with no wasted words. Every piece of information ('List all body styles across categories (raw)', 'Cached 7 days') 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?

Given zero parameters and no output schema, the description is fairly complete. It specifies the purpose, scope, and caching behavior. However, it doesn't describe the output format or any return structure, which could be added for completeness.

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 no parameters, so schema description coverage is 100%. The description adds no parameter information, which is fine since none exist. Baseline score of 3 applies.

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 verb 'List', the resource 'body styles', the scope 'across categories', and the qualifier 'raw'. This distinguishes it from siblings like 'list_body_styles' (likely filtered) and 'list_body_styles_grouped'.

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 provides context ('raw', 'cached 7 days') but does not explicitly state when to use this tool versus alternatives like 'list_body_styles' or 'list_body_styles_grouped'. The hint is sufficient for an agent to infer that this is the unfiltered version.

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