value_by_feed_id

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

Description discloses that tool returns info only if the value block exists, adding context beyond the readOnlyHint annotation. Does not contradict annotations.

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?

Single sentence with no wasted words, front-loading the core action and result condition.

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 tool with one parameter and no output schema, the description sufficiently explains the output concept (value4value, lightning payment, streaming sats) and the condition. Adequate for agent invocation.

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 coverage is 100% and the description restates the parameter's meaning without adding new details. 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?

Description clearly states the tool retrieves value4value information for a podcast using a feed ID, with specific resource ('Podcast Index feed ID') and condition ('if the feed publishes a podcast:value block'). Distinguishes from sibling 'value_by_feed_url' by specifying the input type.

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?

Description implies when to use via the condition 'if the feed publishes a podcast:value block'. Does not explicitly state when not to use or compare with sibling 'value_by_feed_url', but the context is clear.

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