edubase_get_user_organizations

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, which adequately convey the tool's safety and idempotency. The description adds limited detail beyond that, such as the scope of listing all memberships. No contradictions.

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 sentence with 8 words, efficiently front-loading the action and resource. Every word earns its place with no superfluous information.

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 simple lookup tool with one parameter and full schema coverage, the description is sufficient. The presence of an output schema likely documents return values, so the description need not cover that. Minor omission: no mention of empty results or error handling.

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 input schema has 100% description coverage with a single parameter 'user' described as 'user identification string'. The tool description does not add any additional meaning beyond what the schema already provides, adhering to the baseline for full coverage.

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 'List' and clearly identifies the resource 'organizations' with a scope 'a user is member of'. It distinguishes from sibling tools like 'edubase_get_organization' which retrieves a single organization, and 'edubase_get_user' which returns user details.

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 implies usage for retrieving organizations a user belongs to, but provides no explicit guidance on when to use this tool versus alternatives like 'edubase_get_organization' or 'edubase_get_organizations'. No when-not or alternative mentions.

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