Get Organization

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

With no annotations, the description carries the full burden of behavioral transparency. It clearly signals a read-only operation ('Get details') and notes that it accepts either an ID or name, but it does not disclose what 'details' include, authentication requirements, or potential errors.

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 filler. It communicates the action, resource, and parameter semantics efficiently.

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 single-parameter read tool, the description gives enough to call it correctly: identify the organization by ID or name and retrieve details. It lacks an explicit return-value outline, but the term 'details' plus the resource name provides adequate context in the absence of an output schema.

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 coverage is 100% and the orgId parameter is already described as 'The ID or name of the organization'. The description repeats this same information without adding extra meaning, so it meets the baseline but does not elevate it.

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 ('Get details') and a clear resource ('Trello organization (workspace)') with a defined lookup mechanism ('by ID or name'). This distinguishes it from siblings like get_organization_boards and get_member_organizations, which target different resources or scopes.

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 this is the tool for fetching organization-level details, but it does not explicitly state when to use it over alternatives or exclude board/member-specific queries. Sibling names provide context but not explicit routing guidance.

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