edit_scout

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

Annotations already indicate idempotentHint=true. Description adds behavioral detail on status transitions (paused/active/done) and implies mutation. Does not disclose side effects, authorization needs, or confirm idempotency. Adds some value 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?

Two effective sentences: one for purpose, one for status usage. No fluff, front-loaded. Every sentence 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?

Lacks explanation of output or return value (no output schema). Does not mention error conditions, idempotency benefits, or prerequisites (scout must exist). For a tool with 11 parameters and complex status behavior, more guidance is needed.

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 100%, so description adds minimal extra meaning beyond the schema. It provides a usage note on status, but other parameters are adequately described in schema. Baseline 3 is appropriate.

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 explicitly states it updates an existing scout, listing query, schedule, webhook, or status. Provides clear usage examples for status values. Distinguishes from siblings like create_scout and delete_scout.

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?

Provides specific instructions for status values (pause, resume, archive) but lacks explicit guidance on when to use edit vs. create/delete or any prerequisites like scout existence. No mention of alternatives or when not to use.

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