te_list_nodes

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

No annotations provided, so description must cover behavioral info. It only states it searches nodes, implying a read operation. No disclosure of authentication needs, rate limits, error handling, or what happens with invalid filters.

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?

Single sentence is concise but lacks necessary elaboration. It is front-loaded with the main action, but missing details that would justify its length.

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 no output schema, no annotations, and 3 undocumented parameters, the description is too sparse. It does not explain return format, pagination, or how to use filters effectively.

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%, so description must explain parameters. It only mentions filters vaguely. The boolean parameters 'raw' and 'summaries' are not described at all, leaving ambiguity about their effect.

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?

Description clearly states verb+resource: 'Search Tripwire nodes.' It distinguishes from sibling tools like te_get_node (single node) and te_list_versions (versions list). However, it could be more specific by saying 'list all nodes' instead of 'search'.

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?

Description says 'Pass Tripwire query parameters in filters,' which gives minimal usage hint. No guidance on when to use this vs alternatives like te_get_node, no when-not-to-use conditions, and no explanation of required prerequisites.

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