Get poll

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: OAuth integrations require the polls:read scope. It says nothing about the optional expand payloads or rate limits, but the auth scope note is real added value.

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?

Three short fragments with no filler and the core action front-loaded. "Reads account data" is the only soft phrase, but overall the definition is tight and wastes no space.

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?

With no output schema, the description could reasonably say what a poll object contains or what expand returns, and it omits that entirely. It covers the auth scope but leaves the agent to rely on the schema for all retrieval semantics; adequate but with clear gaps for a get-by-ID tool.

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 schema itself documents publication_id, poll_id, account, and all three expand enum values in detail. The description contributes nothing about parameters, so the 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?

"Get poll" is a verbatim restatement of the tool name and title, so the first sentence adds no information. "Reads account data" is vague and does not clarify that this fetches a single poll by publication/poll ID, nor does it distinguish the tool from siblings like list_polls or polls_list_responses.

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 gives no when-to-use guidance, no prerequisites, and never names an alternative such as list_polls for enumeration or polls_list_responses for response data. An agent must infer the single-object-fetch use case entirely from the name and schema.

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