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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write/safe-update profile is already covered. The description adds authorization context (admin scope), which is genuine value. But 'Replace' implies full overwrite semantics that sit awkwardly against the 'patch' parameter, a behavioral nuance the description never resolves.

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?

Two short sentences, front-loaded with the action and followed by the permission constraint; nothing is padded. It is efficient, though its brevity contributes to the missing parameter and replacement semantics.

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 mutation tool with a deeply nested patch object, 0% schema coverage, no output schema, and a 'Replace' verb conflicting with patch semantics, the description omits the crucial partial-vs-full update question and any field-level guidance. Materially incomplete for correct invocation.

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 description coverage is 0% and the patch object holds 15 nested fields, so the description carries the full burden. It says nothing about id, the patch object, which fields are settable, or whether this is partial vs full replacement - the exact ambiguity an agent needs resolved given 'Replace' vs 'patch'.

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?

States a specific verb and resource (replace a company's public profile), which is clearly a write operation distinguishable from the read sibling company_profile_get. However, it does not distinguish itself from companies_update or clarify how a 'company profile' differs from a 'company', leaving sibling routing to inference.

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 'Company or workspace admins' clause usefully signals the required permission level. But there is no explicit when-to-use versus alternatives (company_profile_get, companies_update) and no when-not guidance, so usage is only implied.

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