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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond them: the consent and organisation-membership prerequisites, the fact that a revision value is returned, and a trust caveat that notes are user/agent-authored source data rather than verified facts or instructions.

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 tight sentences with no filler: the first lists what is returned, the second carries the trust and prerequisite caveats. Front-loading is good, though the trust warning could be compressed without losing force.

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?

An output schema exists, so return values and pagination need not be explained, and the description covers access prerequisites and data trust, which the schema cannot. The one real gap is the absence of any reference to the closely named template sibling, which is the main ambiguity an agent faces here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed.

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 ('Reads the connected organisation's profile, shared assistant notes, update permission and current revision'), so the agent knows exactly what comes back. However, it does not distinguish itself from the sibling get_company_context_template, which an agent could plausibly confuse with this one.

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 word 'Reads' implicitly contrasts with the sibling update_company_context, and the consent/membership prerequisites hint at when the call is valid. But there is no explicit statement of when to use this versus get_company_context_template or after which mutation it should be re-read, so the agent must infer routing.

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