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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful scope beyond that: pre-account, in-chat review and the boundary with the official scored photo check. It does not describe the return format, but for a static checklist with no parameters the added behavioral context 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 tight sentences with no wasted wording. The first defines the resource and its scope; the second immediately clarifies the alternative official check.

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 read-only guide with no output schema, the definition covers what it is and when it applies. It could say more about what the checklist contains or returns, but nothing required to invoke it correctly 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?

There are zero parameters and the empty schema is fully covered. The description does not need to explain parameter meaning, so the baseline of 4 applies.

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 the specific resource: DatingProfile's checklist for reviewing dating profile photos shared in chat before account creation. It also distinguishes itself from the official scored photo check that runs on upload, so an agent can tell it apart from sibling get_photo_check.

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?

Gives a clear context for use—reviewing photos the user shares in chat before they have an account—and names the alternative scored check for uploads on datingprofile.app. It does not explicitly say when not to use other photo-related siblings like create_photos or recommend_styles, so it stops short of fully explicit routing guidance.

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