github_apps_get_by_slug

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

No annotations are provided, so the description must convey all behavioral traits. It only states 'Get an app', which implies a read operation but offers no details on authentication needs, error behavior, or return format. This is insufficient for informed agent decision-making.

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 (one sentence), which benefits brevity. However, it is under-specified, sacrificing necessary detail for conciseness. The structure is flat and lacks front-loaded key information. An ideal description would be slightly longer to include essential 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 tool's simplicity (one parameter, no output schema), the description should still clarify what the returned app contains. It fails to do so, leaving agents without understanding of the output or how to use the result. The description is incomplete for a context-aware invocation.

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?

Schema description coverage is 100%, but the parameter description 'app_slug' is merely a label, adding no semantic value. The tool description does not explain what a slug is or how to obtain it. Baseline 3 is appropriate since schema does the minimal documentation, but no additional meaning is added.

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 'Get an app' states a verb and resource, which is clear but vague. It does not distinguish from sibling tools like 'github_apps_get_authenticated' or 'github_apps_get_installation', which also retrieve app-related data. The tool's name includes 'by_slug', but the description omits this important detail, leaving purpose ambiguity.

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 provides no guidance on when to use this tool versus alternative app retrieval tools. There is no mention of prerequisites, context, or exclusion criteria. An agent has no basis to choose this over similar siblings.

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