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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond those annotations – it does not say what 'safety rules' are checked, what happens on failure, whether a text over the length limit is rejected, or how conflicting prose is reported. It is effectively a title echo rather than added behavioral context.

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?

It is a single, front-loaded sentence with no padding, which is structurally clean. But the sentence duplicates the tool title verbatim, so it does not earn its place by adding information.

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-value detail is not required, but this is a complex tool: dual input modes (place vs explicit coordinates), a 30,000-character prose payload, and an undefined notion of 'calculated placements'. None of that is explained. For a 9-parameter audit tool sitting among many similarly named audit/claim tools, the description is too thin to guide 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 description coverage is only 33%, and the description supplies zero parameter meaning. The critical either/or contract – supply 'place' OR the latitude/longitude/timezone triple – is expressed only as an anyOf in the schema, and required fields name, date, time and text carry no explanation of expected formats (date/time string shape, timezoneOffset being a derived fallback). The description does not compensate for the coverage gap.

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?

Tautological: description restates name/title.

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?

There is no when-to-use guidance, no stated preconditions (e.g. that placements must already be calculated before auditing prose), and no mention of alternatives such as audit_prediction_claim for single-claim checks or compare_reading_versions for version diffs. The agent must infer the trigger entirely from the name.

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