Activity descriptions and rates

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

No annotations exist, so the description carries the full behavioral burden. It discloses the shape of the returned data (types plus default rate), but says nothing about pagination, auth requirements, or read-only guarantees beyond the implied 'Lists'. Adequate but incomplete for a zero-annotation tool.

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?

A single sentence with the purpose front-loaded and no filler. The parenthetical is dense but earns its place by defining the resource. Efficient, though slightly packed.

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?

For a low-complexity zero-required-parameter list tool with full schema coverage and no output schema, the description supplies the purpose, the resource definition, and the downstream use case. It is nearly complete, missing only return/pagination expectations.

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 the schema already documents query, flat_rate, and matter_id. The description adds no filter syntax or meaning beyond the schema, which is the baseline 3 case.

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?

States a specific verb and resource (Lists ActivityDescriptions) and immediately defines the resource behaviorally: activity/expense types with their default rate. That definition alone distinguishes it from siblings like clio_time_entries_list. It stops short of naming an alternative sibling explicitly.

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?

Gives a clear usage context: needed to fill in activity_description_id correctly when recording time, which implicitly routes the agent to clio_time_entry_create. No exclusions or explicit alternatives are stated, so it falls just 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.