List records

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

The description adds significant behavioral detail beyond the readOnlyHint annotation: results are flattened out of JSON:API, attributes are hoisted, included records are inlined, and responses include total and nextPage so the agent understands pagination is partial. It also clarifies that report resources return aggregated rows rather than records. This goes well beyond the minimal safety signal.

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 concise at three sentences and front-loads the core purpose. Each sentence provides meaningful information, though the phrase 'Also how the 26 report endpoints are read' is slightly awkward and could be streamlined. Overall it is efficient without unnecessary detail.

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?

With no output schema, the description explains the return shape well: flattened records, inlined relationships, total, and nextPage. It also covers the special report behavior and aggregated rows. For a complex 7-parameter listing tool with 132 possible resources, this is sufficiently complete to guide correct 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?

Schema description coverage is 86%, so the input schema already documents most parameters well. The description adds a little context around group for report endpoints, but it mostly summarizes capabilities like filtering and paging rather than meaningfully extending the schema's parameter documentation. Baseline 3 is appropriate because the schema carries the parameter-semantic burden.

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 the tool lists any Productive resource with filtering, sorting, includes, and paging. It also explicitly handles the special behavior of the 26 report endpoints, distinguishing this from siblings like productive_get and productive_search_capabilities. The verb 'List' and resource scope are unambiguous.

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 gives clear guidance on when to use this tool, including the specific instruction to use resource 'reports/time_reports' with group for aggregated report rows. It provides the main usage context but does not explicitly enumerate exclusions or alternatives such as 'use productive_get for a single record.' The context is clear enough that an agent can choose correctly in most cases.

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