zernio_get_linkedin_organizations

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

No annotations are provided. The description indicates a read operation with no side effects, but does not disclose any behavioral traits such as authentication requirements, rate limits, or potential errors. It is adequate but minimal.

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, front-loaded sentence that contains all necessary information without any extraneous words. It is highly efficient and easy to parse.

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?

Given the low complexity (single parameter, simple get operation) and lack of output schema, the description fairly conveys the tool's purpose. It could mention the return type (list of organizations) but is otherwise complete for the use case.

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?

With 100% schema description coverage for the single parameter, the description adds no additional meaning beyond what the schema already provides. The purpose of 'accountId' is clear from both schema and context, so baseline 3 is appropriate.

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 the action ('Get LinkedIn organization pages') and the resource ('linked to a connected LinkedIn account'), with a specific purpose ('for posting as a company page'). It distinguishes from sibling tools like zernio_select_linkedin_organization and zernio_switch_linkedin_organization which have different actions.

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 provides context about when to use the tool (when you need to retrieve organizations linked to a connected account for posting as a company page), but does not explicitly state when not to use it or list alternative tools. The usage is implied rather than fully guided.

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