feedbin_save_page

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

With no annotations provided, the description carries the full disclosure burden. It does usefully state 'Mutates Feedbin state,' making the write semantics explicit — a meaningful addition since readOnlyHint is absent. However, it says nothing about how duplicate URLs are handled (idempotency), authentication requirements, or what the response contains.

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?

Two short sentences, zero filler, with the core action front-loaded ahead of the mutation caveat. Every word earns its place.

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?

For a simple two-parameter tool with no output schema and no annotations, the essential facts (what it saves, that it writes) are present. But duplicate handling, return value, and the role of the optional title parameter are unaddressed, leaving real gaps for a mutation 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 0%, so both parameters (url, title) are undocumented. The description only implies that a URL identifies the page and says nothing about the optional title argument or whether unknown URLs are fetched server-side, so it fails to compensate for the coverage gap.

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 specific verb and resource: 'Save a webpage as a Feedbin page/entry.' An agent can distinguish it from siblings like feedbin_extract_content or feedbin_cache_entry, though the description doesn't explicitly name the closest alternative.

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 prerequisites, and no mention of when to prefer feedbin_extract_content (which also takes a URL) or feedbin_delete_page for the reverse operation. The agent must infer the selection criteria from the description alone.

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