list_methods

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

No annotations are provided, so the description carries the disclosure burden, but an output schema exists so the return shape is already documented. It does add the important behavioral fact that the tool is deprecated and returns names only, yet says nothing about pagination behavior, permissions, or why it was superseded.

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?

One short sentence, front-loaded with the deprecation warning, then the sole functional fact. Every clause earns its place with no filler.

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?

For a deprecated listing tool with an output schema, the essentials are covered: that it is deprecated, the replacement, and the scope of what it returns. Missing pagination semantics is a minor gap given the tool is discouraged anyway.

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 0% for both parameters, and the description offers no guidance on limit/offset meaning, defaults, or pagination. With two undocumented parameters and no compensating text, the description leaves the schema to speak for itself.

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?

States a specific verb and resource ('Lists function names only'), and the word 'only' hints at a narrower return than a full function listing. It does not explicitly define what a 'method' is versus a function in this domain, but an agent can grasp the operation.

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?

Explicitly marks itself deprecated and names the replacement, list_functions, which is clear routing guidance. It stops short of a full when/when-not statement because, being deprecated, there is realistically no condition under which it should be chosen.

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