list_photos

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

There are no annotations to provide safety context, so the description carries full responsibility. It does not disclose pagination behavior, return format, ordering, or permission requirements. The only behavioral trait is that it 'lists' photos, which is a read operation, but without annotations this is insufficient.

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 a single sentence that is front-loaded with the action and resource. It contains no filler or redundant information and is easily scannable.

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 tool with two parameters and no output schema, the description is too sparse. It does not explain what the returned photo data looks like (e.g., URLs, metadata), whether results are paginated, or how the page parameter behaves. Without annotations or an output schema, the agent is left with significant gaps.

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%, so the description must compensate. It clarifies that school_id refers to the school, but the 'page' parameter is unexplained. The description adds no details about pagination, defaults, or how parameters interact beyond what the schema already shows.

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 verb 'List' and the resource 'photos' with an explicit scope 'posted for a school.' This distinguishes it from sibling tools like list_files or get_post, which are broader or different in purpose.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or compared to list_files or get_post. The intended use is only implied by the tool name and description.

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