Call a Google Photos endpoint directly

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

The description discloses meaningful behavioral traits beyond the annotations: it uses the current access token, and unlike named tools, it does not shape responses, handle pagination, or explain errors. The annotations are neutral on safety, so this added context helps the agent anticipate raw output and error behavior.

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 compact and front-loaded: it defines the purpose in the first sentence, explains the mechanism in the second, and then gives usage guidance. Every sentence contributes value without redundancy.

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 an arbitrary endpoint escape hatch, the description covers the essential context: when to use it, the auth mechanism, and the trade-offs versus named tools. The parameter details are fully handled by the schema, so nothing critical is missing for invoking the tool correctly.

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 input schema already describes all six parameters with full coverage, including enums, defaults, and examples. The description adds little parameter-level detail, but with 100% schema coverage, no additional compensation is needed.

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 defines the tool as an escape hatch for unwrapped Google Photos endpoints, stating exactly what it does: send a path relative to the API root with the current access token. It also distinguishes itself from the sibling named tools by positioning raw as the fallback for API capabilities not yet covered.

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 explicitly says to prefer a named tool where one exists and to reach for raw only when the API has something the tools do not cover yet. This gives the agent a clear decision rule for choosing raw over any sibling tool.

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