Retrieve a public GitHub organization profile by login to enrich company data with organization details.
Retrieve a GitHub organization profile. Returns a public GitHub organization profile (company-side enrichment).
| Name | Required | Description | Default |
|---|---|---|---|
| org | Yes | GitHub organization login |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It mentions 'public' (implies no auth) and 'company-side enrichment', but does not disclose rate limits, required authentication, or any side effects. The behavior beyond a simple retrieval is unclear.
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 extremely concise: two sentences without any redundant information. Every word serves a 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 tool with no output schema, the description should give more detail about what the returned profile contains. The phrase 'company-side enrichment' is vague. The description is incomplete for an agent to understand the output structure.
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 100% coverage with a description for 'org' ('GitHub organization login'), so the description adds no additional meaning. It does not elaborate on the parameter or provide examples or constraints beyond the schema.
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 'retrieve' and the resource 'GitHub organization profile', and adds context 'company-side enrichment'. It distinguishes well from siblings like github_org_repos and github_user.
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?
No explicit guidance on when to use this tool versus alternatives. The purpose is clear, but there is no mention of when not to use it or which sibling tools might be more appropriate for related tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.