hamravesh_database_power

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

No annotations are provided, so the description must disclose behavioral traits. It mentions a disabled state and dry run mode, but does not clarify whether the action is destructive (e.g., shutdown stops database, potentially causing data loss), permissions required, or side effects. This is insufficient for a mutation tool.

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 very short—two sentences and a parenthetical note—and immediately states the core function. However, its brevity sacrifices important details about parameters and behavior. Still, it is efficiently structured for its limited content.

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 the tool has three parameters (two required), no output schema, and no annotations, the description fails to provide sufficient context for an AI agent to invoke it correctly. It does not explain what app_id refers to, what action values mean, or what the response will be.

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 0% description coverage for parameters, and the description does not explain the purpose or acceptable values of app_id, action, or org. It only mentions dry_run and environment variables, ignoring the required parameters entirely.

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's purpose: turning a DBaaS database on or off. It specifies both actions (start/shutdown) and indicates it is disabled by default, requiring activation. It is distinct from sibling tools which focus on apps and other resources.

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 usage context: it mentions that the tool is disabled unless HAMRAVESH_ALLOW_WRITE=1 is set, and it mentions a preview/dry run mode. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it exclude any scenarios.

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