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

Annotations already mark it readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: it clarifies that this returns guidance/schema rather than company data, preempting confusion with the similarly named get_company_context.

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?

Three short sentences, each earning its place: what it returns, what it enables, and what it does not touch. Front-loaded and free of filler.

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 need no elaboration, and the description correctly points at what the response contains (guidance + update schema). Nothing critical is missing for a zero-parameter read tool, though a pointer to the paired update_company_context call would have made it complete.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description's mention of 'the update schema' adds a small amount of meaning about the payload by signaling that the response includes a schema for the companion update tool.

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: returns shared company-context interview guidance plus the update schema. The closing clause ('Does not read or change company records') implicitly separates it from siblings like get_company_context and update_company_context, though those siblings are not named.

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?

'Supports conversation or synthesis from supplied material' hints at the intended workflow but never states when to call this versus get_company_context or get_strategy_template. Usage is implied rather than directed.

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