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

Goes well beyond the readOnly/idempotent annotations: it discloses the required scope (company_context:read), the return shape, the meaning of null, and the non-obvious consequence that turns in a workspace then use no company profile. The workspace-vs-account resolution rule is precisely the hidden behavior an agent would otherwise get wrong.

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?

Front-loaded with the purpose in the first clause, then scope, then return contract, then usage caveats — a sensible order. It is dense but slightly redundant: the parenthetical about turns using no company profile repeats a point already implied by "null means not set."

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?

With only one optional parameter and no output schema, the description still supplies the return object shape, the null case, the auth scope, and the fallback-resolution behavior. An agent can call this confidently on the first try and correctly decide not to call it.

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 already 100%, so baseline is 3; the description earns above that by explaining what workspace_id actually means semantically — it reads that workspace's linked company, only for owned personal workspaces, not an arbitrary partition. That is meaning the schema's "Optional workspace id" line does not carry.

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 ("Read the company profile (Company Context)") and explains exactly what that object is: structured facts used as background for answers. It also cleanly splits the account-level vs workspace-linked read modes. It never names the sibling get_company, so an agent cannot tell from this text alone how this differs from that tool.

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?

Explicit when-to-use ("when the user asks what ISMS Copilot knows about their company or a client"), explicit negative guidance ("Do not call it before a question unless the task needs the user's own data"), and an explicit sequencing rule relative to set_company_context. It even tells the agent not to mention empty results unprompted, which is a real usage decision.

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