get_organization_subscription_details

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. 'Get' implies a read-only operation, but there is no mention of required permissions, rate limits, or what kind of storage details are returned, leaving significant behavioral ambiguity.

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, concise sentence with no filler or redundant wording. It front-loads the core function efficiently, though it offers no additional structure or helpful context.

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?

Given the absence of annotations, an undefined required parameter, and a large sibling tool list, the one-sentence description is insufficient. The output schema exists, so return values need not be elaborated, but the description leaves core input semantics and tool-selection context unresolved.

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 one required parameter, zoid, with 0% schema description coverage. The description does not explain what zoid represents, such as whether it is an organization ID or another identifier, and thus fails to compensate for the complete lack of parameter documentation.

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 states a specific action ('Get') and resource ('organization subscription and storage details'), making the tool's core purpose reasonably clear. However, it does not explicitly differentiate itself from closely related siblings like get_organization_details or get_user_storage_details, leaving some boundary inference to the agent.

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 on when to use this tool versus alternatives such as get_organization_details or get_user_storage_details. The description provides no context, prerequisites, or exclusions to help the agent choose correctly.

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