tdarr_read_plugin

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

With no annotations, the description must disclose behavioral traits, but it only states 'Read a plugin'. It does not mention side effects, permissions, required node state, or error conditions, leaving the agent with no understanding of the tool's operational context.

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 extremely concise at 6 words, with no unnecessary information. It is front-loaded with the action and resource, though it could benefit from a slightly more structured explanation of what 'read' returns.

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 low complexity (1 parameter, no enums), the description is minimally adequate but lacks context about the return value, the format of the plugin object, and how it differs from other plugin-related tools. The absence of an output schema further reduces completeness.

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 single parameter 'plugin' has 100% schema description coverage (described as 'Plugin object'), so baseline is 3. The tool description does not add additional meaning about the expected structure or content of the plugin object, so it meets but does not exceed the baseline.

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 the action 'Read' and the resource 'plugin', with a parenthetical 'used by nodes' providing context. It distinguishes from sibling tools like tdarr_search_plugins or tdarr_read_plugin_text by indicating it reads a full plugin object, though it could mention the return type.

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?

No guidance is provided on when to use this tool versus alternatives like tdarr_read_plugin_text or tdarr_search_plugins. The phrase 'used by nodes' hints at internal use but does not help an AI agent decide between related sibling tools.

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