list_endpoints

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the operation is read-only, what the catalog contains, the output shape, or any auth/rate considerations. For a zero-argument introspection tool, the behavioral profile is almost entirely undisclosed.

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?

It is a single short, front-loaded fragment with no filler, so it is not bloated. However, the brevity comes at the cost of under-specification rather than economy — the phrase is too thin to earn its place.

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 no output schema and no annotations, the description is the only source of information, and it does not say what the returned catalog contains, how entries are structured, or when the result is useful. For an introspection tool this leaves the agent unable to predict the return value.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is no schema surface for the description to explain, and it correctly implies a parameterless enumeration, though it adds no extra meaning.

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 '本MCPのツールカタログ' ('the tool catalog of this MCP') is a noun phrase that roughly restates the tool name list_endpoints rather than stating a clear action+resource. It does not clarify what an 'endpoint' is here or that calling it enumerates available endpoints, and it gives no basis for distinguishing it from siblings such as list_devices or raw_request.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the 15 sibling tools. An agent cannot tell from this text why it would call list_endpoints instead of router_overview or raw_request.

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