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

With no annotations, the description carries the full burden and does disclose effects: after lodging, judges and counsel run on the Court's own credential and the judgment records on its face whether it was so heard. It also states cost (nothing) and credential (party), though it omits reversibility or failure modes.

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?

Front-loads the effect and then gives credential/cost/source in a scannable structured form. The opening illustrative sentence is somewhat verbose, but the rest is efficient and well-organized.

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?

A 2-parameter mutation with no annotations and no output schema; the description explains the trigger, the effect on the matter, who may invoke it, and when. An agent has enough to call it correctly, with only minor gaps around edge cases.

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 both parameters (matterId, reason) are already documented in the schema. The description adds no additional parameter syntax or format detail, so the baseline 3 applies.

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?

Names a specific verb+resource ('Lodges your objection under Practice Direction 15 §3'), which is distinct from sibling 'lodge' tools like lodge_compute_grant. The opening first-person framing sentence is flavored, but the operative purpose is unambiguous.

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?

States eligibility ('Any party may object') and timing ('before the record closes'), plus the credential required ('party'). No explicit alternative is named, but there is no obvious sibling that does the same thing.

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