push_image

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

Description explains the effect of the background parameter (interrupt vs save into rotation), which adds value beyond annotations. However, no disclosure of other behaviors like size validation, device authorization, or potential errors.

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?

Single sentence with parenthetical, front-loaded with purpose. Efficient but could be slightly more structured by separating resolution info.

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?

Lacks output/return value information. With no output schema, description should mention what agent can expect (e.g., success/error). Missing some details like exact image dimension requirements and whether the tool validates inputs.

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?

Adds context beyond schema: background parameter effect explained, resolution constraints provided (64x32; 128x64). Schema already has descriptions for all 4 parameters, so baseline is 3; the extra information lifts it to 4.

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 (push image), input format (base64 WebP), and target (display with resolution constraints). Distinguishes from sibling tools like push_text and push_app.

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 explicit guidance on when to use this tool vs alternatives (e.g., push_app, push_text). The description implies direct display but does not explain when to use background vs foreground or prerequisites.

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