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

Annotations already establish readOnly/idempotent/closed-world, so the bar is lower, yet the description adds real behavioral value: editor_disclosure semantics (current/past/none), that products are company-provided and outside the CC BY dataset, and the agent_access object. With no output schema, this disclosure is genuinely useful rather than redundant.

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 the core purpose ('Full public profile for one organization by slug') before the enumeration. The single sprawling sentence is dense, but in the absence of an output schema each clause about returned fields earns its place.

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 must describe the return payload, and it does so exhaustively: profile fields, funding, people, disclosures, coverage, products with agent_access, lei, licences and certifications. Input and safety are covered by the schema and annotations, so nothing an agent needs is missing.

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 param with 100% schema description coverage ('Organization slug from its URL'), so the schema already carries the meaning. The description only reinforces 'by slug' without adding format or lookup guidance, matching the baseline of 3.

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 (get) and resource (full public profile for one organization) scoped 'by slug', which cleanly separates it from search_organizations. It never names the sibling it is not, but the 'one organization by slug' scope makes the get-vs-search distinction inferable.

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 'by slug' framing implies the precondition (you need a slug in hand) but there is no explicit when-to-use, when-not-to-use, or pointer to search_organizations for discovering a slug. Usage is only implied, not stated.

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