aadc.audit_hardcoded_url

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

With no annotations, the description only states it flags URLs but does not disclose behavioral traits such as whether it modifies files, requires authentication, or what the output format is. Missing context on side effects or error conditions.

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 extremely concise (two sentences) and front-loads the core purpose. Every sentence is essential with no 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?

Given no output schema, no annotations, and nested objects in params, the description lacks completeness. It does not explain the return values, how standards 4 and 6 are applied, or provide examples, leaving the agent underinformed for correct invocation.

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 description does not add additional meaning beyond what is already in the input schema. The description does not elaborate on the parameters, so it meets baseline but does not enhance understanding.

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 flags hardcoded URLs outside the CMS that bypass content review, and references specific standards (4, 6). This distinguishes it from other audit siblings like aadc.audit_launchurl or aadc.audit_permissions.

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 implies usage for detecting hardcoded URLs bypassing CMS review, but does not explicitly state when to use or not use this tool vs alternatives like aadc.audit_all or aadc.audit_link_reachability.

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