Get Cloudways Logs

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

The description only says 'Read recent logs,' implying a non-destructive operation, but fails to disclose important behavioral traits like how 'recent' is defined, authentication requirements, or rate limits. With no annotations, the description carries full burden and falls short.

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 sentence with no unnecessary words. It is front-loaded with the key action and resource. However, it could be slightly more informative without sacrificing conciseness.

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 four parameters, no output schema, and no annotations, the description is incomplete. It does not specify the output format, how many lines are returned (lines parameter), or any filtering behavior. For a log retrieval tool, more context is essential.

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 0%. The description mentions the log types (application, error, access, deployment) which partially explains the log_type parameter, but does not document server_id, app_id, or lines. The enum values are echoed from the schema, adding minimal value.

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 states 'Read recent Cloudways application, error, access, or deployment logs.' It clearly identifies the resource (Cloudways logs) and action (read), and mentions specific log types, distinguishing it from sibling tools like list-cloudways-apps or get-server-stats.

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 provided on when to use this tool versus alternatives such as check-deployment-status or deploy-cloudways-app. There is no mention of prerequisites or context.

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