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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond that: it enumerates what the read returns and flags a provenance caveat that 'products (company-provided, not part of the CC BY dataset)' — a licensing/trust distinction an agent could not get from the annotations.

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?

One sentence, front-loaded with the core operation ('Full public profile for one organization by slug') before the enumeration of contents. Dense but every clause carries information, though the long list of returned sections pushes toward run-on territory.

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?

No output schema exists, so the description carries the return-value burden and does so well by enumerating the profile's sections (funding rounds, people, coverage, disclosure, products). It stops short of any error/not-found behavior or pagination note for large profiles, which leaves a small gap.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. 'By slug' mirrors the schema's own wording and adds no format, casing, or lookup guidance beyond it.

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 ('Full public profile for one organization by slug') plus the title clarifies it covers companies and investors. This implicitly separates it from search_organizations (search vs. keyed fetch), but no sibling is named explicitly, so differentiation is left to inference.

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?

Usage is only implied: 'by slug' plus the schema note 'Organization slug from its URL' tells an agent it needs a pre-known identifier, which mildly implies when this beats a search tool. However, no explicit when-to-use or when-not-to-use guidance and no alternatives (e.g., search_organizations) are named.

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