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

Annotations already declare readOnlyHint and idempotentHint, but the description adds substantial behavioral context: only enumerations are flagged (passing mentions never reported), insufficient_data is returned for missing/BitBucket/unreadable repos, archived repos are skipped, and false drift is avoided. It stops short of disclosing return format or performance characteristics, but the safety and edge-case behavior is rich.

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 lead sentence is a direct question that front-loads purpose, and each subsequent paragraph adds distinct value (rationale, return shape, scope rules, sibling differentiation). It is longer than strictly necessary, with some reinforcement of the 'rotted guidance is worse than none' point, but no genuinely wasted sentences.

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?

An output schema exists, so return values need no explanation. Given the high compleixity of a drift-analysis tool, the description still covers scope exclusions, the enumeration-only rule, and the empty-file result, leaving nothing an agent needs in order to invoke it correctly.

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 the single optional 'repository' parameter is fully documented there, so the baseline applies. The description adds only the default scope ('for each connected repository'), which mildly reinforces the all-repos default but does not extend syntax or meaning beyond the schema.

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 precise verb+resource: judging whether a repo's agent guidance file has drifted from the code it describes, with a concrete example (directories under app/Domain). It explicitly distinguishes itself from the nearest sibling, get-repo-readiness, so an agent can route between the two 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?

Gives explicit trigger conditions — before trusting a guidance file, when onboarding an agent, or when deciding to replace a hand-maintained inventory — and names both the alternative (get-repo-readiness) and the alternative call (get-team-context) with the condition that selects each.

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