Social Set Pfp

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

With no annotations, the description carries the full behavior burden and does well by disclosing the 500x500 cap, the deceptive HTTP 200 error body, the size pre-check, and the SVG rejection. It is missing some details like auth failure or rate limits, but the covered edge cases are highly relevant for successful invocation.

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 front-loaded with the core action, then packs critical caveats into a few purposeful sentences. The Inkscape example is directly actionable, and there is no filler or redundant restating of the tool name.

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 single-parameter tool with full schema coverage and an output schema, the description covers the necessary operational context: session scope, file constraints, failure mode, and SVG handling. An agent has enough information to invoke it 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?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining why the size limit matters, warning that SVG is not accepted, and giving a concrete rasterization command, which helps the agent prepare the file correctly.

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 states a specific verb ('Set') and resource ('profile picture of the active session's account'), which clearly identifies what the tool does. This differentiates it from sibling tools like social_set_bio and project_set_thumbnail, which target different resources.

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 gives clear context: it operates on the active session's account and is for setting the profile picture. It does not explicitly name alternative tools or say when not to use them, but the context is strong enough that an agent can infer the intended use.

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