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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description earns credit by enumerating what the payload contains (seller block, tax id, payment instructions), which matters because there is no output schema.

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?

One tight sentence with the identity-of-the-business framing front-loaded and the returned fields following. No filler, though the fragmentary noun-phrase style costs a little immediate legibility.

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 zero-required-parameter read tool with no output schema, the description adequately signals the return contents and directs the logo question to the parameter. It stops short of noting fields that may be unset or that this is the workspace-wide singleton profile.

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% and the single with_logo parameter carries its own clear explanation (data URL, large, otherwise type/size only). The description contributes nothing about the parameter, so the baseline 3 applies.

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 names the specific resource — the business's own identity as printed on documents — and enumerates its contents (seller block, tax id, payment instructions). It lacks an explicit verb ("get/read"), so a reader must infer retrieval, and it never names the write counterpart core_set_company_profile to draw the line between them.

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?

There is no statement of when to call this versus core_set_company_profile or core_set_company_logo, and no prerequisites or exclusions. The read-only annotations let an agent infer that this is the read side, but the description itself gives no routing guidance.

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