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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real value by disclosing the returned field set and, importantly, the negative behavior that text blocks are omitted. It stops short of stating pagination or result-size behavior, which matters for a list 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?

Three sentences, front-loaded with purpose, then return contents, then routing. The field enumeration is dense but each element is informative; there is no filler, though the middle sentence is long and could be parsed more easily as a list.

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 carries the return-shape burden and does so by naming the fields and the reportId linkage other tools need. The remaining gap is pagination/volume behavior for a list call, which an agent might need to know.

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?

With one parameter at 100% schema coverage, the schema already explains projectId and its provenance (fastero_list_projects). The description adds no further constraint or format detail on the input; its detail about _id/reportId concerns output rather than the parameter.

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 opens with a specific verb and resource ('List the widgets (reports) in a project') and then enumerates exactly which fields come back. It distinguishes itself from fastero_get_report (full read) and fastero_get_dashboard (text blocks), so an agent can separate it from the read-one siblings without inspecting schemas.

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?

It explicitly routes the agent: use fastero_get_report to read one report in full, and go to fastero_get_dashboard for a dashboard's text blocks. That covers the main alternative and the exclusion, though it doesn't state when listing is preferable (e.g., discovery before update) or mention filtering/paging limits.

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