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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get information' without explicitly stating that the operation is read-only or has no side effects, though the tool name includes 'readonly'. It also does not disclose any rate limits, permissions, or the fact that the return varies significantly by method.

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 and free of fluff. However, given the tool's complexity (7 parameters, 9 method variants), it is under-specified; a more structured description that summarizes the method options would be more effective without being verbose.

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 such a rich method enum and pagination options, the description is far too thin. It does not mention that different methods return different data types, how pagination works, or any expectations about the response. The schema fills some gaps, but the description alone leaves an agent without critical context to choose the right method.

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 provides 100% coverage of parameter descriptions, including a detailed explanation of the method enum and pagination parameters. The description adds no extra parameter meaning beyond the schema, so it meets the baseline but does not exceed it.

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 states a clear verb-resource pair ('Get information on a specific pull request'), which is distinct from the sibling tools like get_file_contents or get_me. However, it does not hint at the method parameter's multiple sub-actions (get_diff, get_files, etc.), so the purpose is somewhat broad and not fully differentiated internally.

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 alternatives, nor when not to use it. It does not mention sibling tools or the conditions that would make one method preferable over another. The method parameter descriptions inside the schema give some usage hints, but the tool description itself offers no such context.

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