cache

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

With no annotations, the description carries full burden but only says 'clear all caches' and 'cache config/routes for performance.' It does not disclose side effects, authorization needs, or whether operations are reversible. The destructive nature of clearing is inherent but not explicitly stated.

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 one efficient sentence that front-loads the purpose and lists key operations. No wasted words; every part 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?

The description covers all six enum actions in aggregate: 'clear all caches' can encompass clear, configClear, routeClear, and viewClear, while 'cache config/routes' includes configCache and routeCache. However, it lacks details about return values or operation nuances, but for a simple tool with complete schema, it is adequate with minor gaps.

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 100% for the single 'action' parameter with a clear enum. The description adds performance context for caching operations but does not detail each enum value. It meets the baseline without adding substantial semantics beyond the 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 clearly states the tool manages Laravel caches and specifies 'clear all caches' and 'cache config/routes for performance', which covers the main actions and distinguishes it from generic artisan tools. The verb 'manage' is broad but the specifics make the purpose clear.

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?

No guidance is given on when to use this tool versus alternatives like 'artisan' or 'configGet'. It does not state when to prefer cache operations here or mention any exclusions, leaving usage largely implied by the tool name.

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