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

Despite thin annotations, the description adds meaningful behavioral context: it never invents legal arguments, never drafts/completes filings, never files with a court, and provides an 'honest gut-check.' This goes beyond the annotation flags and sets expectations about output quality and limitations.

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 core is front-loaded and efficient, and the no-drafting/no-filing boundaries are valuable. However, the description is truncated mid-word ('alrea'), ends with pricing/category noise ('10 MESH/call, a tool · legal'), and could be trimmed to a cleaner paragraph.

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?

It lists the output artifacts and audience, which helps an agent set expectations, and it is scoped to a narrow subject domain. But with no output schema and a single generic input field, the missing input contract is a real gap for reliable invocation.

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?

The only parameter, `input`, has schema text that is a generic boilerplate template referencing agent-brain/agent-memory rather than this tool. The description does say the input should be the user's probate/estate facts, which is some added meaning, but it never specifies a shape, optional fields, or whether free-form narrative is accepted.

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?

Description names a specific action (turns disputed probate facts into a case tracker) and enumerates concrete outputs (document inventory, key facts, timeline, next-steps, gut-check). It also draws a bright line against drafting and filing, so the tool cannot be confused with a legal-drafting or court-filing sibling.

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?

Clear intended scenario: use when a user has probate/estate dispute facts and wants a plain-English organizer, targeted at pro se filers and those with counsel. It states what the tool will not do (invent arguments, draft filings, file with a court), but it does not name a specific sibling alternative.

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