list_orgs_for_authenticated_user

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It essentially restates the tool name, adding only the membership scope. It does not mention pagination behavior (page/per_page), return format, authentication requirements, or rate limits, leaving important behavioral traits undisclosed.

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?

The description is a single, front-loaded sentence with no unnecessary words. It is perfectly concise for the minimal information it provides.

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?

Although the tool is simple, the lack of annotations, output schema, and parameter documentation creates significant gaps. The description only states the basic purpose; it does not explain pagination, what data is returned, or any behavioral nuance, making it incomplete for an agent to use confidently.

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?

The schema has two parameters (page, per_page) with 0% description coverage, and the description does not mention them at all. Since the schema provides no meaning and the description does not compensate, the agent gets no guidance on how to use these parameters.

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 clearly states the verb 'List', the resource 'organizations', and the scope 'authenticated user is a member of'. It distinguishes this tool from siblings like list_org_members and get_org by specifying whose organizations are returned.

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 clear context for when to use the tool: to retrieve organizations the authenticated user belongs to. It does not explicitly name alternatives or exclusions, but the wording is specific enough to imply the correct usage context.

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