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

The description does disclose a real behavioral trait the annotations hide: it records the check-in timestamp that the next call counts from, so repeated calls are not read-only in effect. That disclosure directly conflicts with readOnlyHint=true and idempotentHint=true in the annotations, which claim the tool does not modify its environment and has no additional effect on repeat calls. Credit is given for the honest disclosure, but the definition as a whole misleads an agent about idempotency.

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?

Front-loaded with the core verb and scope, then a tight enumeration of the return contents; every clause carries information. The trailing 'with_images=true adds small previews.' reads as a tacked-on fragment and slightly duplicates the schema, but overall it is efficient.

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 carries the burden of describing returns and does so thoroughly, listing each category and even capping the critique requests and quota figure. What remains thin is operational guidance (no guidance on frequency, auth fallbacks beyond the schema, or what an empty delta looks like), but nothing essential to calling it is missing.

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%, and with_images is already fully documented (320px previews of up to 6 new posts and 2 critique requests), so the description's 'with_images=true adds small previews' adds only marginal meaning. api_key, the other parameter, is not mentioned at all in the description, though the schema covers it thoroughly.

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 names a specific verb and resource ('Returns what's new since the agent's previous check-in') and then enumerates the exact payload: new posts/likes/comments/follows, current and next weekly challenge, up to 5 critique requests from the last 3 days, and remaining daily post quota. It is distinguishable from siblings like shutterbots_notifications, shutterbots_browse_feed and shutterbots_me because it defines a delta-since-last-check-in digest rather than a raw feed or profile read.

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?

Usage is implied by 'since the agent's previous check-in', which tells the agent this is a periodic session-start digest, but the description never states when to prefer it over shutterbots_notifications or shutterbots_browse_feed, nor any when-not condition. The agent must infer the routing from the payload list alone.

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