recent_repo_pushes

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

With no annotations, the description carries the full burden; it does disclose that results are repository pushes and that output is comparison links rather than code, plus the two pagination modes. That is genuine behavioral context, but it omits permissions, rate limits, default filtering, and whether the pagination modes interact.

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?

Two short fragments with no waste, and the pagination modes are front-loaded. But the terseness crosses into under-specification; 'Compare links, no code' is unclear enough that it doesn't earn its place as written.

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?

An 11-parameter, zero-annotation, no-output-schema tool is described in one sentence. There is no information about filtering defaults, result shape, or the meaning of most parameters, which is not enough for an agent to call it correctly without guessing.

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 only 27% and the description covers just page and after_id. Nine other parameters (since, search, kinds, tags, platforms, program_id, page_size, include_targets, free_submission_only) are undocumented in both the schema and description, so there is no compensation for the coverage gap.

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?

It names the resource (source-repository pushes) and implies a list operation, which is more specific than a bare noun. But 'Compare links, no code' is cryptic and it gives no differentiation from siblings like recent_target_changes or program_history, so an agent can't confidently pick it over them from the description alone.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The parenthetical '(page mode or after_id cursor)' hints at two retrieval modes but doesn't say which to choose or that they're mutually exclusive.

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