upservice_get_directory_record

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds only the return format (JSON of the record). This is minimal but consistent with annotations. No additional behavioral traits are disclosed beyond what annotations provide.

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 short and front-loaded with the purpose. However, the 'Args' and 'Returns' lines are somewhat redundant given the schema and add no new information. Overall, it is efficiently sized but could be slightly tighter.

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 read-only tool with one parameter and no output schema, the description lacks details like error behavior (e.g., record not found), exact return format, or required permissions. Given the low schema coverage, more is needed to fully guide the assistant.

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% per context, so the description should compensate. It only mentions 'record_id (int)' without adding meaning beyond the schema's own description ('The Upservice directory record ID') or explaining constraints (e.g., required, positive integer).

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 a single directory record by ID.' It uses a specific verb (retrieve) and resource (directory record), and distinguishes from sibling tools like upservice_list_directory_records (which returns multiple) and upservice_get_directory (which retrieves a directory itself).

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 for retrieving a specific record by ID, but it does not explicitly provide when to use this tool versus alternatives (e.g., upservice_list_directory_records for multiple records). No exclusions or context are given.

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