taskhub_orgs_list

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

With no annotations, the description must carry the safety profile itself. 'List' implies a read-only operation and 'your' scopes it to the caller, which is adequate for a zero-parameter list, but it does not explicitly state that no data is modified or what the result includes.

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 one short, front-loaded sentence with no filler. Every word contributes to the tool's purpose.

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, parameterless list operation the description is largely complete: it names the operation and return scope. However, with no output schema or annotations, an explicit note about the response shape or authentication context would make it fully 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?

The tool has zero parameters, so there are no parameters to document beyond the schema. The baseline for a no-parameter tool is 4, and the description adds a useful scoping cue with 'your'.

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 clear verb ('List') and resource ('your organizations'), so an agent knows the tool returns the caller's organizations. It does not explicitly contrast with siblings like taskhub_org_create or taskhub_org_members, though the name and resource make the distinction inferable.

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?

There is no guidance about when to choose this tool over alternatives, no prerequisites, and no exclusions. 'List your organizations' states the operation but leaves the agent to infer the use case and any required auth context.

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