get_organizations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't mention whether this is a read-only operation, whether results are paginated by default, what the response shape looks like, or any rate limits. The 'all organizations' phrasing implies a full listing but no behavioral detail beyond that.

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?

A single concise sentence that front-loads the purpose. No wasted words or redundant information. Could not be meaningfully shorter while retaining its message, making this an appropriately sized description.

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?

This is a relatively simple filtered-list tool with 100% schema coverage and no output schema. The description covers the core purpose adequately. However, with no annotations and no output schema, slightly more context about the return format or pagination default behavior would improve completeness. The schema documents parameters well, so the overall package is functional but minimal.

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%, so the schema already documents all 3 parameters (q, page, itemsPerPage). The description's mention of 'all organizations' and the schema's 'Search query to filter' add some context on how q narrows the result set, but the description itself adds no parameter info beyond what the schema provides. Baseline 3 applies since schema does the heavy lifting.

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?

The description uses a specific verb+resource pattern ('Retrieve all organizations from RogerRoger CRM'), clearly stating the action and source system. It distinguishes from the singular sibling get_organization since it retrieves all organizations, though it doesn't explicitly contrast with that sibling.

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 description provides no guidance on when to use this tool vs alternatives. It doesn't mention that get_organization exists for retrieving a single organization, nor any pagination hints beyond what the schema provides. Context on 'all' vs specific lookup scenarios is absent.

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