whodb_platform_orgs

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered. The description adds useful context (auth-scoped visibility, sequencing after login) and restates read-only, but does not cover pagination or result size. Solid but not adding unusually rich non-annotation behavior.

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?

Short and front-loaded with the core purpose. The final workspace sentence is somewhat redundant with the schema description but still adds workflow context. Minor waste, no fluff.

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?

Output schema exists so return values needn't be explained. The description covers auth scope, sequencing, and targeting well. It omits any note on result size or pagination, but for a discovery-list tool this is close to complete.

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 coverage is 100%, so fields and workspace are fully documented in the schema. The description only hints at field selection ('Prefer fields such as ["id","name","slug","selected"]') and per-call workspace targeting, which the schema's own nested descriptions already cover. 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 (List) and resource (hosted WhoDB organizations), plus scoping ('visible to the authenticated user'). Distinguishable from siblings like whodb_platform_hosts, whodb_platform_projects, and whodb_platform_org_members through the explicit resource and hosted qualifier.

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?

Explicitly states when to use it: 'after whodb login to discover valid organization ids, slugs, and names before selecting a workspace.' Directly chains this into workflow with a concrete downstream action.

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