select_linkedin_organization

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

With no annotations, the description must fully convey behavior. It only states 'select' without explaining side effects (e.g., whether it sets a session, changes state, or returns data). The agent is left guessing what 'select' entails.

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?

A single sentence of 10 words conveys the core purpose. No unnecessary words, and the action-resource pair is front-loaded. This is highly concise.

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 description lacks completeness for a tool with 4 parameters and no output schema. It does not explain the effect of selection (e.g., does it return confirmation?), the optional logo URL's purpose, or the state change. Given tool complexity, more detail is needed.

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?

All parameters have descriptions in the schema (100% coverage). The description adds no additional meaning beyond the schema, such as the role of organization_logo_url or constraints on organization_id format. Baseline score of 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 specifies the verb 'select' and the resource 'LinkedIn company page'. It conveys the tool's role in choosing an organization for posting, distinguishing it from sibling tools like 'get_linkedin_organizations' (listing) or 'generate_post' (creating posts).

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 after retrieving organizations, but does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites (e.g., must have an organization list) or exclusions.

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