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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no further behavioral context such as rate limits, pagination behavior, or failure modes. It does mention the ordering ('newest first') and return format, which are functional details, but not beyond what annotations and schema already imply. This is adequate but not rich.

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 exactly two sentences, front-loaded with the purpose and context, and the second sentence efficiently covers filters and output fields. There is zero fluff or redundancy; every word earns its place.

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?

Since there is no output schema, the description's listing of returned fields (cause number, court, case type, decoded status, filing date, both parties, both attorneys) is essential and complete. Filters are described, and ordering is explicit. The only minor gap is that the schema example includes a 'days' parameter not referenced in the description or schema properties, but this is an inconsistency in the tool definition rather than a description deficiency. Overall, the description is sufficiently complete for a read-only listing 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 description coverage is 100%, so all four parameters (court, limit, case_type, filed_after) are already documented with descriptions and examples. The description adds meaning for case_type and court ('Optionally filter by case_type... or court number') but does not add anything about filed_after. The 'newest first' ordering is useful context but pertains to the tool behavior rather than parameter semantics. Baseline 3 is appropriate since the schema does the heavy lifting.

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 identifies the tool as returning recently filed Harris County civil cases with a specific ordering (newest first) and defines its niche as 'the what is being filed in Houston right now view.' It names the resource (Harris County civil cases) and distinguishes it from siblings like harris_civil_case (single case lookup) and harris_civil_search_party (party search), even listing the returned fields (cause number, court, case type, status, filing date, parties, attorneys).

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 a clear context for use ('what is being filed in Houston right now') and specifies optional filters (case_type, court). It does not explicitly state when not to use this tool or name alternatives, but the use case is strong enough that an agent can infer when it is appropriate compared to searching for a specific party or case. No exclusions are mentioned.

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