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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'Public org profile', which implies a read-only operation returning public data, but it does not state whether authentication is needed, what fields are returned, or any rate-limit considerations. The word 'public' hints at safety, but nothing explicit is disclosed.

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 short five-word phrase with no filler or redundant information. It is front-loaded and efficient, making it easy to parse. However, it is a noun fragment rather than a complete sentence, which slightly reduces clarity compared to a well-formed sentence.

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 tool with one optional parameter and an output schema, the description is minimal but still incomplete. It omits parameter semantics and fails to explain what a 'public org profile' contains. While the output schema may supply some return details, it cannot compensate for the missing usage and parameter guidance. The description is barely more informative than the title.

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 input schema has one parameter 'q' with a default value and 0% schema description coverage. The tool description does not explain what 'q' means; an agent must infer from the context that it is probably the organization name or identifier. This is a clear gap because the description was expected to compensate for the missing schema 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 'GitHub Org: Public org profile' identifies a specific resource (public profile of a GitHub organization) and implies the operation of fetching that profile. It is distinguishable from siblings like ghrepo or ghcommits, which target repositories and commits. However, it lacks an explicit verb such as 'get' or 'retrieve', making it slightly less direct than an ideal purpose statement.

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 gives no guidance on when to use this tool versus alternatives. With a large sibling list of GitHub-related tools (ghrepo, githubsearch, ghcommits, etc.), an agent receives no criteria for selecting this one. No exclusions, conditions, or alternative tool names are mentioned.

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