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

Annotations only declare the generic mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds substantive behavior beyond that: fetch-once-then-store (never hotlinked), a 300 KB size cap, accepted formats, the company-profile prerequisite, and the crucial fact that changing the logo re-brands past documents while frozen seller data and amounts stay fixed. It also states the effect summary.

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 intent is front-loaded in the first sentence and each following sentence carries facts (storage model, formats, size cap, prerequisite, removal). The 'Branding, not a fact' aside is slightly discursive, but it earns its place by explaining retroactive re-branding.

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 three-optional-parameter mutation with no output schema, the description covers inputs, storage semantics, constraints, prerequisite, and the resulting effect ('company logo stored (or removed)'). Nothing an agent needs in order to call it correctly is missing.

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 per-parameter meaning is already documented, giving a baseline of 3. The description adds value the schema does not: the file-vs-URL choice is presented as mutually alternative input modes, and remove=true is framed as the inverse operation rather than just another flag.

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 opens with a specific verb and resource: 'Put your logo on the invoice document', then enumerates the two input routes (file upload, public https URL) and the removal path. It is unmistakably distinct from core_set_company_profile among the siblings.

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?

It gives clear conditions for each mode: upload a file OR supply a public https URL, and 'Pass remove=true to take it off'. The prerequisite 'Needs a company profile first' is an explicit precondition. It stops short of naming a sibling alternative explicitly, which keeps it at 4 rather than 5.

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