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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a non-obvious behavioral constraint beyond the annotations: only 'public' details are returned, and callers must 'preserve returned URLs exactly' — a real instruction about handling output that structured fields do not convey.

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 short, front-loaded sentences with no filler: the purpose first, then the output-handling caveat. Every clause 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?

An output schema exists, so return values need not be described, and the single required parameter is fully documented. The only remaining gap is the lack of differentiation from the numerous get_* siblings, which would help an agent over a larger toolset.

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?

Schema description coverage is 100% for the single parameter, and the schema already explains that the slug is 'returned by search_organizations'. The description adds only the word 'organization' as qualifier, so it neither compensates for a gap nor adds meaningful syntax or format detail. Baseline 3 applies.

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 ('public details for one AI organization'), plus the keying parameter (slug). It is distinguishable from the sibling search_organizations, but among the many 'get_*' siblings (get_company, get_model, etc.) it does not explicitly articulate what makes an 'organization' distinct from those entities.

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 phrase 'by slug' plus the schema note 'slug returned by search_organizations' implicitly chains this after a search, which is useful routing. However, there is no explicit when-to-use statement or when-not guidance relative to the other get_* siblings.

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