poll_connector

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

No annotations exist, so the description must carry the burden of behavioral disclosure. It states that the tool triggers a poll and fetches data, but does not disclose whether it is destructive, if it requires specific permissions, rate limits, or what side effects occur (e.g., overwriting previous data).

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 extremely concise (one sentence), but this brevity sacrifices essential information. It is underspecified, not efficiently 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 tool is simple (one required parameter), and an output schema exists (so return values don't need explanation). However, the description lacks context about error scenarios, expected behavior when connector is unavailable, or typical usage patterns. It is minimally adequate but incomplete.

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%, meaning the schema provides no documentation for the single parameter. The description does not explain what 'connector_id' is or how to obtain it, beyond the minimal schema title. The description adds no value for parameter understanding.

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?

Description clearly states the action ('Trigger an immediate poll') and the resource ('a connector'), with the parenthetical clarifying the purpose ('fetch latest data from the source'). This distinguishes it from related sibling tools like create_connector, get_connector, or test_connector.

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?

No guidance is provided on when to use this tool versus alternatives, such as checking if a connector is already polling or when to use test_connector instead. Prerequisites or exclusions are not mentioned.

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