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

Beyond the annotations, the description discloses the external side effect (sending data to the LexLint team), the account linkage, the sign-in or UnGovr Open Data key requirement, and the one-submission limit. It also flags the serious privacy risk of building the usage summary from the session transcript because a pasted key would be transmitted.

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 purpose is front-loaded, followed by the safety and approval constraints. Despite the length, every sentence carries operational weight: approval gating, the single unprompted context, the headless prohibition, the transcript warning, and the one-per-session limit.

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 an external-side-effect mutation tool with no output schema, the description covers purpose, authorization requirements, privacy hazards, approval workflow, and rate limiting. An agent has everything needed to decide whether to invoke it and how to construct the payload safely.

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%, so parameter meanings are already documented. The description still adds meaningful semantics by constraining how usage_summary must be produced, especially the warning not to read the session transcript, and by requiring the exact payload to be printed and sent only if approved unchanged.

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 first sentence states a specific verb, resource, and recipient: sending developer feedback on LexLint to its builders, recorded against their UnGovr account. This is unmistakably distinct from siblings such as run_lint, upload_lint_run, and set_profile, so no schema opening is needed to identify the tool.

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 rules: only on the developer's explicit yes, unprompted in exactly one place, never elsewhere, and never in headless or CI sessions. It also specifies the approval workflow and the one-submission-per-session limit, leaving nothing to inference.

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