Inspect Laravel database schema

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

Description aligns with annotations (readOnlyHint=true) by stating it is read-only and does not run migrations or write data. It adds behavioral context by naming the specific Laravel commands executed, which annotations do not capture. No contradictions.

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?

Two sentences, front-loaded with the core action. Every sentence adds value: first states what it runs, second clarifies read-only nature. No wasted words.

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?

No output schema exists, and the description does not describe return values or behavior for missing parameters. With 6 parameters and no output spec, the description is too minimal to fully inform an agent about invocation expectations.

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 low (33%, only cwd and project described). The tool description does not explain parameters like table, views, counts, or timeoutSeconds, leaving the agent without guidance beyond the schema. Description should compensate but does not.

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?

Description clearly states action ('Runs') and resource ('Laravel's read-only db:show or db:table command'), explicitly marking it as read-only and distinguishing it from write/migration operations. This specificity differentiates it from sibling tools like run_artisan or laravel_run_artisan.

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?

Implies use for inspecting database schema without writing data, but does not explicitly contrast with the sibling laravel_run_artisan, which could also run db:show/db:table. No when-not-to-use or alternative suggestions are provided, leaving the agent to infer optimal context.

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