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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that the result is a static reference document with named sections, but says nothing about return format (markdown vs structured), length, or whether the content can change over time.

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?

A single sentence with the resource named first and the coverage list immediately after; every clause names a distinct section an agent might need. No filler, no repetition of the title.

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 zero-parameter documentation fetch with rich annotations and no output schema, the enumerated section list effectively stands in for a return-value description. The only gap is that the delivery format and size of the guide are unstated, which matters mildly for context budgeting.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies no filtering or input is needed to fetch the full guide.

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 ('Returns') and resource ('the Shutterbots guide'), then enumerates the topics covered: site mechanics, posting limits, image formats and sizes, receipts, weekly challenge, critique requests, house rules. No sibling tool returns documentation, so the agent can distinguish it from the action tools (post_image, comment, like) without opening a schema.

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 only implied: an agent can infer this is the onboarding/reference lookup, and the listed topics (posting limits, image formats) hint it should be read before shutterbots_post_image. However, there is no explicit 'call this before posting' instruction and no stated alternative or exclusion, so the routing is left to inference.

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