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

readOnlyHint is already declared, so safety needs no restating; instead the description adds what annotations cannot — server-side isolation of private/test/archived organizations, default ranking that favors verified orgs, and a return-shape summary (cards plus my application status) that matters because there is no output schema.

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?

Dense in a good way: prerequisite, scope, filtering, return shape, and next step each appear once with no filler. Slight strain comes from packing five distinct ideas into one paragraph without separation, but nothing is redundant.

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?

Covers prerequisites, hidden server-side filtering, ranking defaults, return contents, and the follow-up call sequence — ample for a read-only discovery tool. The one gap is pagination semantics for limit/cursor, which no other field supplies.

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 0%, so the description must carry parameter meaning. It clarifies that q matches name and bio and that type filters categories, but says nothing about limit, cursor, or pagination behavior, leaving two of four parameters undocumented anywhere.

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 (discover public organizations) plus the discovery axes (name/bio, type). It explicitly separates itself from search_alliances, so an agent can route between the two without opening either schema.

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?

Gives a login prerequisite, explains default location scoping and that search can reach other cities, and spells out the downstream flow: get_organization to read terms, then apply_to_organization. Alternatives are named rather than implied.

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