What this checkout hands your agent

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

No annotations are provided, so the description carries the full burden. It clearly explains the tool returns a 'headline count' (not detailed content) and enumerates exactly what categories it covers. It does not explicitly state read-only behavior, but the nature of a count implies it, and all listed items are inspection targets.

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?

The description is two sentences, front-loaded with 'Start here,' and every word adds value. It concisely lists the included categories and provides usage context without any fluff.

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 summary tool, the description fully covers its scope, purpose, and when to use it. Given the simple one-parameter schema and no output schema, it provides sufficient context for an agent to select and invoke the tool correctly. The sibling tools are implicitly referenced by the categories listed.

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?

The input schema already provides 100% coverage with a clear description of the 'dir' parameter. The tool description does not add additional meaning beyond the schema, so it meets the baseline but does not go beyond it.

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?

The description clearly states the tool provides a 'headline count' of agent-related items in a directory, listing specific categories (instruction files, hook commands, MCP servers, etc.). This is a specific verb+resource and distinguishes it from sibling tools that likely drill into individual categories.

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?

Explicit guidance is given on when to use: 'Use before working in a repo you did not write, or when reviewing a PR that touches agent config.' The phrase 'Start here' also signals this is the intended entry point before using more specific sibling tools.

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