get_company_details_uid

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

No annotations provided; description mentions no authentication needed and use of UID webservice, which implies read-only behavior, but lacks details on side effects, rate limits, or return format.

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?

Two concise sentences, front-loaded with purpose, no redundancy.

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?

No output schema and description only says 'detailed company information' without specifying fields or structure. Lacks differentiation from sibling tool 'get_company_by_uid', leaving agent guessing.

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 100%; the parameter 'uid' is fully described in schema. Description adds no extra parameter meaning, so baseline 3 applies.

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 'Get detailed company information' using UID, differentiating from other tools by mentioning a specific webservice and no authentication requirement. However, sibling tool 'get_company_by_uid' exists with similar name, so distinction is not explicit.

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?

Indicates when to use (when you have a UID and want detailed info) and that no Zefix auth is needed, but does not provide when-not or compare to alternatives like 'get_company_by_uid'.

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