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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds nothing behavioral: no indication of auth requirements, pagination, result shape, or what an audit flag represents. The operation ID string is identifier metadata, not 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?

The same sentence is repeated twice verbatim, wasting half the text, followed by an opaque operation hash. There is no front-loaded purpose statement beyond the raw endpoint path.

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?

No output schema exists, so the description should describe the returned audit flags and the query-filter capability; it does neither. With a nested free-form query object and zero parameter documentation, an agent has no way to call this correctly beyond passing an id.

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 0% for 2 parameters, so the description must compensate and does not. The ':id' in the path weakly implies the required lease id, but the free-form 'query' object (additionalProperties with no documented keys) is left entirely unexplained.

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 echoes the REST path 'GET /api/leases/:id/audit-flags', which does encode a verb (fetch) and a resource (audit flags for a specific lease). But it is a verbatim restatement of the title and never explains in plain language what 'audit flags' are or how they differ from the sibling get_leases_by_id_audit_logs.

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 only guidance offered is 'describe_operation provides native request schemas', which is a pointer to a schema-lookup helper, not a when-to-use rule. There is no statement of when this endpoint should be chosen over get_leases_by_id_audit_logs or get_leases_by_id_field_changes.

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