Resume Postgres instance

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

The description states 'Resume' which implies a state change, but does not disclose any behavioral traits such as idempotency, error conditions, or potential side effects. The annotations show readOnlyHint=false, which is consistent, but no additional context is provided.

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 extremely concise at two sentences. It efficiently conveys the action, resource, and API endpoint. No unnecessary information is included.

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?

For a simple mutation tool with one parameter and no output schema, the description is adequate but incomplete. It misses behavioral context such as idempotency or error handling. The presence of annotations helps slightly, but the description adds minimal extra value.

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 is only one parameter, 'postgresId', with no description in the input schema. The tool description does not elaborate on its meaning or format. The schema coverage is 0%, so the description should compensate but fails to do so.

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 action 'Resume' and the resource 'Postgres instance', and includes the API endpoint. It distinguishes from siblings like 'render_suspend_postgres' by specifying the exact operation.

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 lacks any guidance on when to use this tool. It doesn't mention prerequisites, alternatives, or situations to avoid. The sibling tool 'render_suspend_postgres' implies this is the reverse operation, but no explicit instructions are given.

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