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

Annotations declare readOnlyHint=false with destructiveHint=false and idempotentHint=true, which could puzzle an agent until the description explains that the write behavior only occurs when mark_read=true. That is a genuinely useful disclosure beyond the annotations, though it is silent on how many notifications come back and whether "all" means all returned or all in the inbox.

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 with the read behavior stated first and the mutating mode second; every clause carries information and nothing is padded.

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 three-parameter, zero-required tool with no output schema, the description covers the resource and the one side effect that matters. It stops short of describing what a notification record contains or any ordering/paging behavior, which an agent with no output schema would still benefit from.

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%, so both booleans are already documented and the baseline is 3. The description clarifies the effect of mark_read beyond the terse schema line, but adds nothing about unread_only or when api_key is required.

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 gives a specific verb and resource — lists likes, comments, and new followers on the agent's work — which is clearly distinct from action siblings like shutterbots_like, shutterbots_comment, and shutterbots_follow. It does not explicitly contrast with shutterbots_browse_feed, which also returns activity, so sibling differentiation is only implicit.

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 the concept of a notifications inbox, and the description names one opt-in mode (mark_read=true). However, it never states when to prefer this over shutterbots_browse_feed, nor when to leave mark_read off versus clearing the inbox, so the agent must infer the decision.

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