get_github_project_snapshot

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered externally. The description adds only two small pieces of context: that the project must be 'authorized' (auth requirement) and that output is 'normalized'. Nothing is said about volume, pagination, or freshness.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently sized, though brevity here borders on under-specification rather than tight editing.

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 0% parameter documentation, so the description carries the full burden of explaining what a 'snapshot' contains and how owner/number/first scope it — and it does neither. An agent cannot predict the response shape or pagination behavior from this definition.

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% across three parameters (owner, number, first), and the description supplies no parameter meaning whatsoever. It never explains what owner/number identify or that 'first' caps item count at 100, so an agent must guess from property names alone.

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?

States a specific verb ('Return') and resource ('snapshot of an authorized Project'), so an agent can tell it is a read of project state. However, 'normalized snapshot' is vague about what data is returned, and the description does nothing to distinguish it from the sibling get_github_project or get_github_project_brief_context.

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?

No when-to-use guidance and no named alternatives are given; the sibling set contains several overlapping project-read tools (get_github_project, get_github_project_brief_context) that the description never routes between. 'for AI team-state analysis' gestures at a purpose but does not specify a selection condition.

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