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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the meaningful behavioral fact that it takes no arguments and always resolves to the caller's own organization, but discloses nothing about response freshness, permissions, or limits.

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 sentences, front-loaded with what is returned, then why it matters. The second sentence is somewhat long with nested parentheticals, but every clause carries usable guidance.

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-value details are already covered and the description need not restate them. For a zero-parameter, annotated read-only tool, the definition supplies enough context for correct invocation, though it omits any note on how current the profile data is.

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, the baseline is 4, and the description reinforces this by explicitly stating 'No arguments — it is always the caller's organization', which pre-empts an agent hunting for an org or company ID. No further parameter meaning is 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?

The description names the resource precisely and enumerates its contents (company name, summary, category, products/services with features, benefits, USPs), so an agent knows exactly what it gets. It does not explicitly differentiate itself from a sibling like org_documents, which keeps it just below a 5.

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?

It states when to use it — grounding ideation and strategy such as new project ideas, positioning, and what to ask next — with concrete examples. There is no explicit when-not guidance or named alternative, but the usage context is unambiguous.

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