ecosystem_scan_status

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

No annotations provided to indicate safety or destructiveness. The description does not disclose any behavioral traits (e.g., idempotency, caching, access requirements) beyond the basic fetch action, leaving agents without sufficient context.

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 clear sentence with no extraneous words. However, it is minimal and could be slightly more informative without losing conciseness.

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 fetch-by-ID tool, the description is acceptable but lacks any context about when to use it relative to siblings. The presence of an output schema compensates partially, but guidance is missing.

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% (the only parameter 'run_id' is described in the schema). The description adds no additional semantic value beyond the schema's own field description.

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 'Fetch a single EcosystemScanRun by id' clearly states the action (Fetch) and the resource (a specific EcosystemScanRun by its ID). It is distinct from sibling tools like ecosystem_scan_history (list history) or ecosystem_scan (initiate scan).

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?

No guidance on when to use this tool versus alternatives such as ecosystem_scan_history or ecosystem_deep_review_status. The description lacks context about prerequisites or typical use cases.

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