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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description still adds real context by disclosing the returned fields and the empty-list state that warrants create_company. It does not describe pagination or ordering, so it falls short of a 5.

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 purpose and payload fields, then the cross-tool wiring. It is dense but every sentence carries information; the final create_company sentence is the least essential yet still actionable.

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 no output schema, the description compensates by listing the fields returned, and it covers the empty-list case and default-company semantics. An agent has everything needed to call this tool and interpret the result.

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 the baseline is 4. The description's discussion of company_id concerns other tools rather than this one's schema, but it usefully clarifies the default-company resolution behavior an agent will encounter immediately downstream.

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 ('List the user's company/product context profiles') and even enumerates the returned fields (id, name, summary, audience, key facts). It does not explicitly distinguish itself from the sibling list_profiles, which is a minor differentiation gap given how closely named the two are.

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?

Highly explicit: it names the downstream tools that consume company_id (create_outline, generate_content), states the omit-to-use-voice-default and pass-null-for-none semantics, and routes to create_company when the list is empty. Nothing about when to use this tool is left to inference.

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