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

With no annotations, the description carries the full burden and does well by noting 'metadata only, no source body' and detailing exactly what counts are provided. It implies read-only behavior but does not explicitly state 'no side effects' or mention auth/rate limits, which are not relevant here but could be more explicit.

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 a single dense sentence that front-loads the purpose and enumerates specific metrics. It is somewhat long but every clause adds information; it could be improved with bullet points, but it remains efficient and free of 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 stats tool with no parameters and no output schema, the description is quite complete: it lists all major metrics, the scope ('every application-source program'), and the intended first-use context. It does not specify the exact output format (e.g., JSON fields), but that is minor given the descriptive enumeration.

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 tool has zero parameters, so the baseline score is 4. The description correctly does not attempt to document parameters, and the schema already covers the empty parameter list fully.

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 it provides an 'Overview of the Ross ERP 8.0 program catalog' with a specific list of metrics (totals, TITLE id counts, table links, read/write counts, etc.). This distinguishes it from sibling tools like list_programs or lookup_program, which deal with individual programs or listings.

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 final line 'Use this first to orient before browsing programs' gives explicit guidance on when to use the tool. It does not explicitly name alternatives or provide when-not-to-use exclusions, but the context implies it precedes other browsing tools.

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