get_catalog_element

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

No annotations are provided, and the description only states the action without disclosing behavior such as read-only status, error handling, permissions, or return format. It implies a read operation but does not explicitly confirm safety or edge cases.

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, front-loaded with the action and resource, with no redundant words.

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 with two well-described parameters, but the description lacks explicit guidance on return shape or error behavior; however, for a read operation the core purpose is conveyed sufficiently.

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?

Both parameters are already fully described in the schema (id as GUID Ref_Key, catalog_name as the catalog name). The description adds no additional parameter semantics beyond restating 'Ref_Key' for id.

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 'Отримання повних реквізитів елемента довідника' (obtaining full details of a catalog element) and specifies the identifier format 'Ref_Key (GUID)'. This clearly distinguishes from siblings like search_catalog and create_catalog_element.

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 Ref_Key and need full element details, but it does not explicitly state when to prefer this over search_catalog or mention exclusions.

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