Systemonomic

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation (implying read-only) and mentions output includes 'timestamps and summaries', but doesn't cover critical aspects like pagination, sorting, error conditions, authentication needs, rate limits, or whether it returns all runs or only recent ones. For a list tool with zero annotation coverage, this leaves significant gaps.

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 a single, efficient sentence that front-loads the core purpose ('List all ATSS assessment runs for a project') and adds useful output details ('with timestamps and summaries'). There is no wasted verbiage or redundancy.

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?

Given the tool has an output schema (which should document return values), the description doesn't need to detail outputs. However, with no annotations and low parameter schema coverage, the description should do more to explain behavior and usage. It adequately covers the basic purpose but lacks guidance and behavioral context, making it minimally complete for a simple list tool.

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?

The description mentions 'for a project', which aligns with the single parameter 'project_id' in the schema. However, schema description coverage is 0%, so the schema provides no parameter details. The description adds minimal semantic context (it's project-scoped) but doesn't explain what a project ID is, its format, or where to find it. This partially compensates but not fully for the coverage gap.

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 action ('List all ATSS assessment runs') and resource ('for a project'), with additional context about what information is returned ('with timestamps and summaries'). It distinguishes from some siblings like 'get_atss_results' (which likely retrieves detailed results) and 'run_atss_batch' (which executes runs), but doesn't explicitly differentiate from all siblings like 'list_tasks' or 'list_suggestions'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not scenarios, or compare with sibling tools like 'get_atss_results' (for detailed results) or 'persist_atss_results' (for saving results). The agent must infer usage from the tool name and description alone.

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