Add a photo to a project from a local file

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

Given no annotations, the description fully discloses the multi-step process (read file, mint S3 URL, PUT bytes, attach) and that no credentials are needed. Notes aspect ratio constraint. Missing potential side effects like overwriting, but overall transparent.

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?

Concise 4-sentence paragraph. Front-loads purpose, explains process, then constraints. Every sentence is informative with no 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?

No output schema, but parameters are well-documented in schema. Description covers workflow and constraints. Could mention error cases or size limits, but fairly complete for its complexity.

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 coverage is 100%, so baseline is 3. The description adds context about local file path and aspect ratio, but does not elaborate on optional parameters beyond schema descriptions.

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?

Clearly states the action: 'Upload a LOCAL image file to a project.' Distinguishes from siblings by emphasizing the credential-less local upload path not possible via remote MCP. Includes constraints like aspect ratio and read-only block.

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?

Explicitly notes this is the 'credential-less upload path the remote MCP can't do,' guiding when to use it. Also mentions 'Blocked in read-only mode.' Lacks explicit alternatives but provides clear contextual usage.

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