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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a small behavioral hint about 'privacy-filtered' output, but it is vague and does not specify what filtering applies, what the return payload contains, or any limitations. With annotations carrying the load, this is adequate but not rich.

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 sentence, which is concise, but it is poorly structured and under-specified. It does not front-load the core purpose clearly (the phrase 'hosted get github app status' is awkward) and leaves the reader to parse the intended meaning. It is short but not effective.

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?

There is no output schema, and the description does not state what the tool returns (e.g., a status object, a JSON blob, or a simple string). It also fails to explain how the three parameters relate to the operation or what 'status' means in this context. Given the large number of sibling read tools, the description is insufficient for an agent to call it confidently.

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 0%, and the description does not explain any of the three parameters (projectId, sessionId, executionId). Since the schema only provides patterns and no descriptions, the description should compensate by explaining how these IDs map to the operation, but it does not. The phrase 'using privacy-filtered project metadata' hints at projectId being relevant but does not clarify the others.

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 verb 'Read' and the noun phrase 'hosted get github app status' indicate a read operation for GitHub app status, but the phrasing is awkward and ambiguous. It does not clearly differentiate from sibling tools like get_project_status or get_agent_execution_status; the mention of 'privacy-filtered project metadata' is vague and does not explain what the tool actually retrieves.

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 any of the nearly 100 sibling tools. It does not state prerequisites, context, or exclusions. An agent cannot determine whether this is the right tool for a given task without additional inference.

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