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

No annotations, so the description carries the burden, and it clearly signals a read-only inspection ('Read this project's git state'). It discloses the scope of returned data and its role as a pre-flight check, though it says nothing about permissions or behavior when the project has no repo/remote configured.

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?

Front-loads what the tool reads, then the when-to-use guidance, in two dense sentences. The parenthetical REST path earns its place by giving the alternative configuration route.

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 read-only single-param tool with an output schema, the definition covers purpose, contents, and usage routing fully. Nothing needed to call it correctly is missing, and return values are documented in the output schema.

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 coverage is 0% for the single required project_id param, but the description's repeated 'this project' framing gives implicit meaning to that argument. It adds little beyond the self-evident identifier, so it neither compensates nor misleads.

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 (read) and resource (this project's git state), then enumerates the exact fields returned: remote URL, branch, HEAD sha, ahead/behind counts, uncommitted changes, oversized files. This lets an agent distinguish it from sync_from_git without opening either schema.

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?

Explicitly says 'Read this before sync_from_git to decide whether a pull is needed or the remote still has to be configured', naming the alternative tool and the decision it informs. It even supplies the fallback configuration path when no remote is set.

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