othos_organization_list

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

No annotations provided. Description straightforwardly indicates a read-only list operation with no destructive side effects. Lacks detail on return format or data volume, but adequate for a simple listing.

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?

Single sentence with no redundancy. Front-loaded with verb and resource.

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?

For a parameterless list tool with no output schema, description adequately states function and scope. Could mention return format (e.g., list of organization IDs/names) but not essential.

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?

No parameters in schema. Description adds no parameter info beyond purpose, but baseline for 0 parameters is 4. Schema coverage is 100% trivial.

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?

Description clearly states verb 'List', resource 'organizations', and scope 'available for the authenticated user'. Distinct from siblings like othos_organization_current (current org) and othos_organization_change (change org).

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?

Implied usage for retrieving all accessible organizations. No explicit when-not or alternatives mentioned, but context differentiates from sibling tools that retrieve current org or change it.

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