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

No annotations are provided, so the description carries the full burden. It discloses that results are paginated, but says nothing about permissions, rate limits, result ordering, or what a page contains and how to detect the end of the list. For a list tool with zero annotation coverage this is thin.

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?

Two short sentences, front-loaded with the scope statement followed by the practical tip; nothing is padded. Minor misspelling ('Recurents') and the lack of any second sentence on return shape keep it from a 5.

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 annotation and no output schema, the description must at least imply the pagination contract, and it only states that results are paginated without explaining how to move through pages or what a page holds. Adequate for the basic call, incomplete for correct iteration.

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 page, size, and account_code are already fully documented with defaults and bounds. The description's size advice adds a small amount of practical meaning but largely restates the default value, fitting the baseline 3 when the schema does the heavy lifting.

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?

Names a specific verb (list) and resource (pieces), and disambiguates the jargon by enumerating what a 'piece' is (Tasks, Stories, Recurents), scoped to an account. It does not explicitly contrast with siblings like ListProjectsTool or GetPieceTool, so it stops short of a 5.

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?

Offers operational advice ('Start with size 10; use size 5 for large pieces') but this is tuning guidance, not when-to-use guidance. Nothing says when to call this versus GetPieceTool for a single item or ListProjectsTool for projects, so usage is only implied.

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