Retrieve Postgres instance

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

Annotations already provide readOnlyHint=true, idempotentHint=true, etc. The description adds 'Calls GET /postgres/{postgresId}', confirming a safe read operation. However, it does not disclose any behavioral traits beyond what annotations imply, such as rate limits or data potentially returned.

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 consists of two sentences: a one-line summary and a line specifying the HTTP call. It is concise and front-loaded with the purpose. Every sentence serves a function, but could be slightly more structured.

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 tool is simple (1 required parameter, read-only), but there is no output schema and the description does not explain what is returned. For a retrieval tool, knowing the response structure would aid an AI agent. The annotations cover safety but not completeness.

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 one parameter (postgresId) with 0% description coverage. The description only says 'by ID' without explaining the format, source, or context of the ID. No additional semantics are provided beyond the schema's type and requirement.

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 'Retrieve Postgres instance' and 'Retrieve a Postgres instance by ID', specifying the verb and resource. Among sibling tools like render_retrieve_blueprint and render_retrieve_service, the name and description distinguish it by focusing on 'postgres', making differentiation straightforward.

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 implies usage when you have a postgres ID and want instance details, but it does not explicitly state when to use this tool over alternatives (e.g., use render_retrieve_postgres_connection_info for connection info). No when-not guidance is provided.

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