Get organization

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value by saying which categories of settings come back, but says nothing about rate limiting, permission requirements, or failure behavior for a non-allowlisted org.

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?

A single front-loaded sentence with zero filler and the returned setting categories listed in a compact parenthetical. Nothing is redundant, though it is dense enough that a skimming agent may miss the scoping implication.

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 one-parameter read with strong annotations and no output schema, the description is adequate: it hints at what the payload contains. It does not indicate response shape, whether unknown orgs error, or how this differs from the posture/assessment siblings, leaving a modest gap.

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?

There is a single parameter and schema description coverage is 100%, including the GHE_ORG_ALLOWLIST constraint. The description adds no additional meaning about the 'org' identifier (format, case-sensitivity, login vs name), so it sits at the schema-backed baseline.

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?

Specific verb + resource ('Fetch an organization's full profile'), and it enumerates the security settings it returns (2FA, base permission, secret scanning & Dependabot defaults), which distinguishes it from list_organizations and from narrower siblings like get_actions_permissions. It stops short of naming the closest alternative, assess_org_posture, so the boundary is not fully drawn.

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?

Usage is only implied by 'full profile and security-relevant settings'; there is no explicit statement of when to pick this over assess_org_posture or list_organizations. No preconditions (e.g., allowlist, permission level) are mentioned in the description, though the allowlist constraint is carried by the schema.

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