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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: newest-first ordering, the distinction between generations and uploads, and the fact that uploads are the only way to access local files. It doesn't mention pagination or exact return shape, but for a read-only list tool this is solid.

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 sentences, front-loaded with the core behavior, and the second sentence earns its place by explaining the uploads workflow. No fluff.

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 read-only list tool with no output schema, the description covers the main use cases and the uploads workflow. It doesn't describe the return format or pagination, but the annotations cover safety and the schema covers parameters. Slightly more detail on what fields are returned (e.g., r2Path) would make it fully complete, but it's already strong.

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 coverage is 50%: the 'type' parameter has a description, but 'limit' does not. The description adds context for 'type' (uploads lists source photos, not generations) and explains the r2Path pickup, which goes beyond the schema. The 'limit' parameter is still undocumented in the description, but its meaning is fairly obvious from the schema (default 20, max 50).

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 lists the user's recent generations, or uploaded source photos when type='uploads', newest first. It distinguishes itself from siblings by explaining the uploads case and why it matters (connectors cannot send bytes).

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?

It explicitly says when to use the 'uploads' type: when the user refers to a photo they added but have not run a tool on yet. It also explains the workflow context (user adds at pixly.app/app, tool picks up r2Path), which is strong guidance for an agent deciding between this and other tools.

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