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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), and the description adds real value on top: the required permission (org.compliance.manage, OWNER+/ADMIN+), the ENTERPRISE+ tier gate, and the returned content (current step, step name, history timeline). It stops short of pagination or volume limits, keeping it from a 5.

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?

Single dense paragraph that front-loads scope and resource before the filter, return shape, endpoint, and permission. Every clause carries information, though the packed run-on style slightly reduces scannability.

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?

With no output schema, the description usefully specifies the return shape, and it covers tier gating, permission, and filtering. Only pagination/result-size behavior is absent, which is a minor gap for a list tool.

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 schema already declares the enum and default, so baseline is 3; the description earns one more by clarifying what the values mean, namely that status=all includes resolved rows while active filters them out.

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?

States a specific verb (list) and resource (in-flight TimesheetEscalation rows) with clear org scope, and the ENTERPRISE+ qualifier plus the sibling resource names distinguish it from list_compliance_exceptions, list_timesheet_entries, and weekly_compliance.

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?

Implies usage via the default-active behavior and the org-wide scope, but never states when to reach for this tool versus adjacent ones like list_compliance_exceptions or weekly_compliance, and offers no explicit exclusions or prerequisites beyond the permission note.

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