cortex_get_organization

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

The description adds a behavioral constraint ('requires superadmin API key') but does not explicitly state read-only nature or other side effects. With no annotations, the description partially covers behavioral transparency but lacks depth (e.g., no mention of idempotency or rate limits).

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, efficient sentence with no unnecessary words. Every word contributes to the purpose and constraint.

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?

No output schema is provided, and the description fails to explain what 'details' are returned (e.g., fields like name, status). The description is insufficient for an agent to fully understand the tool's behavioral output.

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?

Input schema has 100% description coverage for the single parameter ('orgId'). The description does not add meaning beyond what the schema already provides, resulting in a baseline score of 3.

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 ('Get'), resource ('organization'), and a key constraint ('requires superadmin API key'). It distinguishes from siblings like 'cortex_list_organizations' and 'cortex_update_organization' by specifying a single organization retrieval.

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 fetching a specific organization's details but does not explicitly provide when-to-use or when-not-to-use guidance relative to siblings. No exclusion criteria or alternatives are mentioned.

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