feedbin_get_import

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses almost nothing: it does not say the call is a safe read, whether a pending import requires repeated polling, how item statuses are represented, or what happens for an unknown import_id. Only the phrase 'import and its item statuses' hints at the response shape.

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?

One short, front-loaded sentence with no padding. It is arguably too terse rather than verbose, but nothing in it is wasted.

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 annotations and no output schema, the description is the only source of truth about behavior and return values, and 'item statuses' is unexplained. For a single-parameter read tool this leaves a meaningful gap an agent must guess around.

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% for the single required parameter import_id, which has no type-descriptive title beyond 'Import Id'. The description implies the id selects one import but adds no format, source, or example of where such an id comes from (presumably from create_import or list_imports).

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?

States a concrete verb+resource: retrieve a single OPML import plus the per-item statuses belonging to it. That distinguishes it adequately from feedbin_list_imports and feedbin_create_import, though it never names those siblings explicitly.

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?

There is no when-to-use guidance, no mention of when to prefer feedbin_list_imports, and no prerequisites (e.g. auth, whether the import must already be in progress). An agent must infer the usage pattern entirely from the word 'one'.

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