ecosystem_repo_manual_status

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

No annotations provided, so the description carries the full burden. It discloses that this is a write/mutation operation ('Set (or clear) the human override') and mentions 'stored for audit' for the reason parameter, which is useful. However, it doesn't disclose whether this is destructive, whether it can be reversed, what permissions are needed, or what happens to previously set values when clearing. It also doesn't describe response behavior despite having an output schema.

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 compact and well-organized, with the core statement in the first line and supporting context about the historical consolidation following. Every sentence adds value. Minor inefficiency: the historical-tool context, while valuable, could be slightly tighter, but it's justified given the consolidation rationale.

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 a write-operation tool, no annotations, and an output schema present, the description should still clarify behavior. It explains the purpose well but omits guidance on the output schema semantics, error conditions, authorization needs, or reversibility of the override. The consolidation context helps a lot, but for a mutation tool the behavioral gaps are noticeable.

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%, so the schema documents all four parameters. The description adds meaning by explaining that the status argument's ``pinned`` / ``no_value`` values map to the old distinct tools (pin_active, mark_no_value) and empty string clears. It also clarifies reason is 'recommended when setting,' adding guidance beyond the schema. This is a genuinely helpful layer beyond the structured schema.

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 verb+resource: 'Set (or clear) the human override on a repo's active status.' It also provides valuable context by explaining this tool consolidates four historical tools that posted identical payloads. However, it doesn't explicitly name the sibling 'ecosystem_mark_as_reference' or 'ecosystem_repo_get' to differentiate, though the historical-tool context does distinguish it from other ecosystem 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?

The description explains that this is the single entry point for all manual verdicts and that four historical tools (pin_active/unpin/mark_no_value/clear_manual_status) are consolidated here, mapping to the status argument values. This gives clear guidance on the semantic range of operations. It doesn't explicitly state when NOT to use it versus read-only tools, but the context about being the only manual-status tool is reasonably clear.

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