Get a Twenty CRM record

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds 'Read-only' which is consistent, but does not provide additional behavioral context beyond what annotations already convey. No contradiction.

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, clear sentence without any unnecessary words. It is front-loaded with the key action and immediately follows with the read-only qualifier. No fluff.

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?

Although the tool is simple, the description omits details about return format, error handling, and parameter nuances (e.g., depth, response_format). No output schema is provided, so the description should at least mention what the agent can expect as output. The openness of the tool (openWorldHint) also suggests more context about potential side effects or data freshness would be helpful.

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 coverage is 75%, so the input schema documents most parameters. The description does not add any parameter-specific meaning or context beyond what the schema already provides. Baseline of 3 is appropriate given the high schema coverage.

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 'Fetch one record by object name and UUID' and includes 'Read-only', which distinguishes it from write siblings like twenty_create_record or twenty_update_record. The verb 'fetch' and resource 'record' are specific, but it could be more explicit about when to use this tool versus twenty_list_records or twenty_search_records.

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 usage guidelines provided. The description does not indicate when to use this tool over alternatives such as twenty_list_records or twenty_search_records. It only describes the operation without context about when it is appropriate.

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