Get Power_port_template

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety. The description adds value by specifying return formats (Markdown or JSON with nested references) and that it returns the full object. No contradictions. A 4 reflects that the description provides useful behavioral context beyond annotations.

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 concise: three sentences covering purpose, usage, and return format. No unnecessary words. Every sentence adds value, and the structure is clear.

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 simple nature of a get-by-id operation, the description is complete. It specifies what the tool does, when to use it, and what it returns (Markdown or JSON with nested references). With good annotations and no output schema, this is sufficient for an agent to use correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining the 'id' parameter is numeric and that 'response_format' controls output (markdown for human, json for chaining). This goes beyond what the schema provides, justifying a 4.

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 'Get a single power_port_template from NetBox by numeric id.' This is a specific verb+resource, and it distinguishes from sibling tools like list/create/update/delete by focusing on retrieval by id. It also provides usage context (after list or when you have id).

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 explicitly says 'Use after netbox_list_power_port_templates has located the object, or when you already have the id.' This gives clear context for when to use this tool. It also hints at response_format usage for chaining, but does not provide explicit exclusions or alternatives, so a 4 is appropriate.

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