hello_aigent_fetch

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

The description discloses key behavioral traits: signature verification against feed's public key, separation of verified and unverified updates, and stripping actions from unverified ones. This goes beyond the absent annotations, though it could elaborate on cursor management.

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 concise, two sentences, with the core purpose front-loaded. Every sentence adds value without redundancy.

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?

Given no output schema, the description explains the return format (two arrays: updates and unverified) and verification behavior. It is mostly complete, though lacks details on cursor updates or pagination.

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?

Input schema has 100% coverage, with both parameters described in the schema. The description does not add additional parameter meaning, so it meets baseline expectations but does not excel.

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?

The description clearly states the tool fetches new updates for a subscription using a stored cursor, specifying the verb 'fetch' and resource 'new updates'. It distinguishes itself from sibling tools (list, subscribe, unsubscribe) by focusing on retrieving updates.

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 implies usage after subscribing, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. It could mention not to use for listing or modifying subscriptions.

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