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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful context: the status is from an external third party, not the vendor, and it mentions a relay disclaimer and citation requirement. The wording around the disclaimer is vague, but it is useful behavioral information beyond the annotations.

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 short and front-loads the core purpose, but it is highly compressed and telegraphic. Fragments such as 'bar, 7 days' and '★Relay disclaimer and citation★' reduce readability rather than earning their place as clear guidance.

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?

There is no output schema, so the description must explain return content. It lists several returned components, including conclusion, vendor notices, editor's check, user reports, status page URL, and same-vendor states, but some items remain cryptic and the relationship to status_history is not addressed.

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%, so the slug parameter is already documented as a system slug from renkeimap_find_system. The description adds useful semantics for omitting the slug: without it, the tool returns systems with a notice or anomaly now.

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 that the tool returns the status of one system, specifically as observed externally by IT連携マップ rather than by the vendor. It is more specific than a tautology, but it does not explicitly distinguish itself from the sibling renkeimap_status_history.

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 implies this is for checking current status, and it notes the no-slug behavior for systems with a notice or anomaly now. However, it gives no explicit guidance on when to use this versus renkeimap_status_history or renkeimap_system_facts.

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