ecosystem_scan_profile_update

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

The description contradicts itself: it says 'writes are no-op' yet also says 'create a new ScanProfile version'. No annotations are provided, and the behavioral implications (e.g., whether the previous version is actually deactivated) are not clarified. The true behavior is obscured by the contradictory statements.

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 front-loaded with the deprecation notice, which is good, but it includes unnecessary technical details (e.g., 'alert_thresholds.max_new_per_scan') that could be shorter. The contradictory creation line adds confusion. It is not as concise as it could be.

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 complexity and the availability of an output schema, the description provides a migration path and states the no-op behavior. However, the contradictory creation statement undermines completeness. The description could be clearer about what the tool does (nothing) and why it exists.

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 input schema has 100% coverage for the single parameter, and the schema description already states the parameter is ignored. The description adds no extra semantic value beyond what the schema provides. Baseline score of 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?

The description claims to 'create a new ScanProfile version' but also states the tool is deprecated and writes are ignored. This contradiction makes the actual purpose unclear. The title is null, so there is no additional clarity.

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 deprecation notice explicitly provides a migration path to use the settings API/UI and states that writes are ignored. This gives clear guidance to avoid using this tool and use an alternative instead. However, the remaining creation line may cause confusion.

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