list_methods

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function without mentioning side effects, safety (read-only), authentication requirements, rate limits, or output specifics. The existence of an output schema does not excuse the description from providing at least a high-level behavioral overview.

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 a single sentence with no filler words. It is front-loaded with the verb and resource, making the purpose immediately clear. Every word earns 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?

Given the tool's low complexity and the presence of an output schema (which likely documents return values), the description is minimally adequate. However, it lacks details on default behavior, case sensitivity, or pagination. For a simple list with two optional filters, this is acceptable but not rich.

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%, and the description only names the parameters ('search', 'namespace') without adding meaning. It says 'optionally filtered by namespace/search' but does not explain what values are acceptable, how filtering works (e.g., partial match), or defaults. This adds minimal value beyond the parameter names.

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 states 'List pylzt API methods, optionally filtered by namespace/search.' It clearly specifies the verb (list), resource (pylzt API methods), and the filtering options. This distinguishes it from sibling listing tools that target different resources (subscriptions, flows, etc.).

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 provides no explicit guidance on when to use this tool versus alternatives. With many sibling 'list_*' tools, such as list_subscriptions or list_flows, the agent would benefit from contextual clues about selecting this specific tool for API methods. The description only implies usage without exclusions or comparisons.

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