List photos

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

Annotations already indicate a safe read-only operation. The description adds that output consists of direct image URLs and that these are intended for use with get_post or download_file, which is useful behavioral context beyond the schema.

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 brief with no redundant words, but the first sentence is a fragment ('Photos and photo albums...') rather than a complete sentence, which slightly reduces structural clarity.

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 list tool with two optional parameters and an output schema, the description covers the core purpose and gives actionable integration advice. It does not mention pagination or sorting, but the schema and output schema likely cover those.

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?

Both parameters are fully described in the schema (page, school_id), and the description does not add any additional parameter-specific meaning. Since schema coverage is 100%, the baseline of 3 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?

The description identifies the resource ('photos and photo albums shared by the school') and notes they come with direct image URLs, but it uses a noun phrase rather than an explicit verb like 'lists'. The title 'List photos' supplies the action, and the mention of downstream use in get_post/download_file distinguishes it from generic file listing tools.

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 a usage tip about passing URLs to get_post or download_file, but it never states when to choose this tool over siblings like list_files or get_post, nor does it mention any exclusions. Usage context is implied by the resource type.

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