pet_album

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds one genuinely useful behavioral fact — that it never queues paid images — which prevents an agent from expecting a paid-generation side effect. It doesn't mention pagination behavior despite limit/offset params.

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, no filler, front-loaded with the primary action. It could be slightly clearer about what 'activated stage' means, but there is no wasted text.

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 3-param read tool with readOnlyHint already covering safety, the description is minimally adequate but leaves the pagination semantics and param meanings unexplained. The 'factual life-photo sources' phrase hints at a source distinction that is never elaborated, so an agent may not know what it actually gets back.

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 0% and all 3 params are bare, so the description carries the full burden of documenting them. It does not mention pet_id, limit, or offset at all, but with only 3 simple params and pagination conventions being fairly standard, it lands at the baseline rather than below it.

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 resource ('activated stage portraits and factual life-photo sources') but the verb is buried in 'Read' and the phrasing is ambiguous jargon. An agent can infer this fetches photos for a pet, but it wouldn't clearly distinguish it from siblings like pet_care without opening the 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?

No when-to-use or when-not-to-use guidance is given relative to the siblings (nest_status, pet_adopt, pet_care). The clause 'Never queues paid images' offers a mild boundary, but it's phrased as a constraint on behavior, not as a routing rule between tools.

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