update_self_diagnosis

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

No annotations are provided, and the incomplete description does not disclose behavioral aspects such as side effects, permissions, or read-only nature. The tool likely returns state without mutation, but this is not explicitly stated.

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 very short but incomplete, cutting off mid-sentence. It lacks essential information, making it under-specified rather than concise.

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 that there is no output schema and the description is incomplete, the tool lacks sufficient context. For a diagnostic tool, it should detail the returned health state information, but it fails to do so.

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?

No parameters in the input schema, so the description does not need to add parameter details. Schema description coverage is 100% (empty). The baseline score of 4 is appropriate as no additional meaning is required.

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 begins with 'Returns the self-update health state' suggesting a read operation, but the name 'update_self_diagnosis' misleadingly implies a write/update action. The description is cut off, providing incomplete information about what the tool does.

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 like 'update_local_mcp' or 'run_diagnostics'. No exclusions or context provided.

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