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

The annotations declare readOnlyHint=true, and the description does not contradict that. It adds a valuable behavioral caveat: 'There is no service-method extension in criminal motions; rule 4.111 does not provide one,' which prevents an agent from assuming a civil-style extension applies. This goes beyond what annotations already convey, though it does not describe output details or other side effects.

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 three sentences, with the primary computation stated first, the secondary outside-deadline feature second, and a crucial caveat third. Every sentence earns its place and there is no redundant or filler text. It is efficiently front-loaded.

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?

The description covers the core computation and the outside-deadline tracks, and the no-extension caveat is essential legal context. There is no output schema, but the listed output components (service, proof, opposition, reply, hearing) give a good picture of what is returned. The parameter semantics are fully handled by the schema, so nothing critical is missing for an agent to invoke it correctly.

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 each of the four parameters already has a clear description. The tool description does not add parameter-specific semantics beyond the schema; it mentions service/opposition/reply/hearing in the context of the output, not parameter meaning. This matches the baseline 3 for full schema coverage.

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 uses the specific verb 'Compute' with a precise resource ('California Rule of Court 4.111 briefing chain for a criminal pretrial motion') and lists the computed items. It clearly distinguishes from the sibling california_motion_deadlines by specifying 'criminal' and the rule number, so an agent can tell them apart without opening schemas.

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 provides clear context: it is for criminal pretrial motions under CRC 4.111 and also covers outside deadlines for trigger-event motions. However, it does not explicitly name alternatives or state when not to use it, such as pointing to california_motion_deadlines for civil motions. The context is clear but lacks exclusions, so it stops short of a 5.

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