List Projects & Activities

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

With no annotations provided, the description carries the disclosure burden. The verb 'Get' implies a read-only operation, and it mentions the data sources and returned fields. However, it does not explicitly state safety (e.g., no side effects), rate limits, or pagination behavior, leaving some behavioral details implicit.

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 a single, concise sentence that starts with the primary action and resource, then lists relevant data fields. Every phrase adds value, and there is no redundancy or wasted text.

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?

Despite having no output schema and no annotations, the description covers what the tool does, the data sources, and the fields returned. The schema handles parameter documentation, including the non-paginating API behavior via max_records. Missing details like response structure or ordering are minor for a list operation.

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 parameter descriptions fully document each filter. The tool description adds no extra meaning beyond the schema, which is acceptable given the schema works well alone.

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 clearly states a specific verb ('Get') and resource ('project/activity costing entries'), with an explicit note that these come from timesheets and expenses. It also lists the key data fields, distinguishing itself from sibling tools like list_timesheets or list_expenses.

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 conveys the context of use by indicating that this returns consolidated costing entries from timesheets and expenses. It does not explicitly mention when not to use it or name alternatives, but the clear scope is sufficient for distinguishing it from related tools.

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