List run properties

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

Annotations already declare readOnlyHint=true, so the read-only nature is established. The description adds behavioral context by specifying the output is name/value properties and explaining the optional filter scope, which goes beyond the annotation.

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?

Extremely concise at two short sentences. The first sentence 'TestRun.properties.' is slightly redundant as a label, but the overall description is front-loaded and free of waste.

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?

For a simple one-parameter read tool with readOnlyHint, the description adequately conveys purpose, optional filtering, and return value shape. No output schema exists, but the description's 'name/value properties' sufficiently covers expected return content.

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 coverage is 100% with run_id already documented as 'Test run id. Omit to list properties without a run filter.' The description repeats this filter concept but does not add additional meaning beyond the schema, so 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?

Description states it returns name/value properties for a run, with a clear verb ('Returns') and resource ('run properties'). It differentiates from sibling tools by specifying 'run', distinguishing it from case and execution properties tools.

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?

Provides clear context: use to list run properties, and explains the optional run_id behavior ('Omit to list properties without a run filter'). No explicit alternatives or exclusions, but the run-scoped context is sufficient for straightforward selection among siblings.

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