git-mcp-server: Get operation

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds details: 'no repository input required', 'lookup only', and lists exclusions, providing behavioral context beyond annotations. No contradiction.

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?

Three sentences: purpose+returns, defaults, exclusions. Front-loaded with key action. No unnecessary words. Efficient structure.

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?

Output schema exists, so return values are covered. Description specifies what is returned, defaults, and exclusions. Adequate for a simple read-only tool, though could mention when to use in relation to sibling tools (implied but not explicit).

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 100% and schema description of request_id is detailed. Description adds 'Read the result stored for request_id' but essentially restates schema's purpose. No new semantic meaning beyond what schema provides.

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?

Description clearly states 'Read the result stored for request_id' - specific verb 'Read' and resource 'result'. Distinguishes from sibling git mutation tools which perform actions; this only reads stored results.

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?

States 'Defaults: lookup only; no repository input required' and lists exclusions like 'Git execution, repository mutation'. Provides context for when to use (retrieve result) and when not to (perform git operations), though could be more explicit about use case for checking previous mutations.

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