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

No annotations are provided, and the description 'Profile Photos' discloses no behavioral traits: no mention that it is a read operation, no explanation of pagination, no note on what data is returned. The description carries the full burden for behavioral transparency and fails completely.

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?

The description is two words with no content; it is under-specification rather than conciseness. It fails to earn its place because it adds nothing beyond the tool name, and there is no front-loaded actionable information.

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?

With 3 parameters (1 required), no output schema, and no annotations, a description of 'Profile Photos' is completely inadequate. It does not explain what the tool returns, how pagination works, or any expected behavior, making this definition severely incomplete.

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 schema has 100% description coverage: url is described as 'Facebook page URL', and cursor/next_page_id are described as pagination controls. The description adds no additional semantics beyond the schema, so the baseline score of 3 is appropriate.

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 is just 'Profile Photos', which is a noun phrase restating the tool name. It lacks a specific verb and resource, and does not distinguish this tool from many similar scrapecreators tools like scrapecreators_basic_profile or scrapecreators_instagram. It is a tautology.

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?

The description provides no guidance on when to use this tool or which alternatives to prefer. It does not state any context, prerequisites, or exclusions, leaving the agent without any decision support beyond the tool name.

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