repository_status

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

With no annotations, the description carries the full burden and discloses the key behavioral trait: no network operations are performed. This signals a read-only, local operation, though it does not mention error behavior for non-repository paths or any implicit side effects.

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 sentence that front-loads the action and resource, then adds the crucial network-avoidance constraint. Every word earns its place with no filler.

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 one-parameter local inspection tool with an output schema, the description is largely complete: it states the operation and the important safety boundary. Minor ambiguity about path parameter expectations is acceptable given the descriptive property name.

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%, and the description adds no parameter-level meaning beyond the property name 'repository_path'. The name implies a local path, but the description does not clarify path format, absolute vs relative, or repository constraints.

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 and resource: 'Return local Git status'. The qualifier 'local' and the explicit exclusion of 'fetch, pull, or other network operations' clearly differentiate it from siblings like repository_fetch, repository_pull, and repository_clone.

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 clearly communicates that this tool is for local-only status inspection and should not be relied on for network operations. It does not explicitly name an alternative for when remote synchronization is needed, so it stops short of full when/when-not guidance.

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