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

Annotations already cover the read-only, non-destructive profile, and the description goes well beyond them: it discloses the 50-item cap, newest-first ordering, absence of paging, the full status vocabulary with an explicit note that succeeded/failed/cancelled are terminal, the triggeredBy categories, and the savedFiles artifact. That is substantive behavioral context an agent cannot get from the annotations.

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 that front-loads the key constraint (50 most recent, newest first, no paging) before the field enumeration. The trailing field list is long but every clause earns its place because there is no output schema to convey return shape.

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 full burden of describing returns, and it does so thoroughly — run identity, entrypoint, status semantics, trigger origin, timestamps, error, and output files. Combined with the schema's parameter docs, an agent has everything needed to invoke and interpret the call.

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% and both parameters (projectId, pythonProjectId) are documented in the schema with their source tools. The description adds no syntax or format detail beyond that, so the baseline 3 is appropriate.

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 and resource (list Python runs), pins the scope (50 most recent, newest first, no paging), and explicitly identifies the sibling fastero_get_python_run_log as the consumer of the returned _id. An agent can distinguish this from the many other list_* siblings without opening a schema.

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?

Clear context: this is the way to enumerate recent runs, and its _id feeds fastero_get_python_run_log, which routes the agent between the two. It also rules out paging. It stops short of an explicit when-to-use/when-not statement against other list tools, so it lands just below the top.

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