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

Annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavioral context: it runs pre-compile, requires no D365 install, returns a violation table with severity/rule/code/fix, and warns that auto-fixing Critical violations requires D365_CUSTOM_MODEL_PATH. This goes well beyond the annotations.

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 dense but every sentence serves a purpose: core purpose, rule categories, execution model, exclusions, alternatives, return format, and a prerequisite caveat. It is longer than ideal, but the information is organized and front-loaded; no meaningful filler exists.

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 tool with no output schema, the description fully covers the return value ('violation table: severity, rule ID, code snippet, fix instruction'), execution context, exclusions, alternatives, and a credential/path prerequisite. An agent has enough context to invoke the tool correctly and interpret its result.

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 100%, so the schema already documents all three parameters with defaults and examples. The description mentions severities and the object scope but does not add significant meaning beyond what the schema provides, so the baseline score of 3 applies.

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 opens with a specific verb-resource pair: 'Run an in-house best-practice audit on any AOT object.' It immediately distinguishes itself from the Microsoft BP checker and names sibling tools with different purposes, so an agent can tell exactly what this tool is for.

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 gives explicit when-to-use and when-not-to-use guidance: use it for pre-compile, in-house checks without a D365 install, but for the authoritative Microsoft verdict use run_best_practices_check or run_best_practices_check_scoped, and for deep N+1 profiling use detect_performance_issues. It also notes it does not replace xppbp.exe.

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