get_matter

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action without mentioning that it is a read-only operation, what permissions might be required, or what happens if the ID does not exist (e.g., returns null vs error).

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 very short (5 words) and free of clutter, but it sacrifices informational value. It is appropriately concise for a simple tool, but could include a bit more context without becoming verbose.

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?

Given that there is an output schema, the description need not detail return values, but it should at least state that it returns a matter object. The description is too minimal given the existence of many similar sibling tools; it does not help the agent differentiate when to use this versus other get tools.

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 input schema has 0% description coverage; the parameter 'matter_id' lacks a description. The tool description repeats 'by ID' but does not add any detail about the format, expected length, or meaning of the ID, failing to add value beyond the schema.

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 'Get a matter by ID' clearly states the verb (get), resource (matter), and the selection criterion (by ID). It distinguishes from list_matters (which returns multiple matters) and other get tools that target sub-resources like get_matter_archive or get_matter_billing_configuration.

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?

No explicit guidance on when to use or alternatives. The description implies usage when a matter ID is available, but does not mention that list_matters is for browsing or that other matter-specific get tools exist for different needs.

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