context_verify

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

Discloses that it checks commits in the server's repo and lists classification categories ('merged', 'present-unmerged', etc.). No annotations exist, so description carries full burden; it is adequately transparent.

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, front-loaded with the core action. Every sentence adds value, though the parameter gap detracts from efficiency.

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?

Covers main purpose, classification, and git integration. However, missing parameter explanation for 'segment' leaves the description incomplete for a tool with one parameter.

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?

Description does not mention the 'segment' parameter at all. Schema description coverage is 0%, and the description offers no meaning beyond the schema, leaving the agent guessing about its purpose.

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 'list and classify change entries against GIT', specifying verb and resource. Differentiates from siblings by focusing on git-based completion integrity, though not explicitly contrasting with similar tools.

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?

Provides implicit usage context by stating that logging 'fixed' is insufficient; done means merged. However, no explicit when-to-use or alternatives are given.

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