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

With no annotations, the description carries the full burden and handles it well. It clarifies this is a retrieval operation that returns the full script source plus a setup snippet — not an operation that executes the kill switch — which prevents a likely misinterpretation of 'get_killcord.' It also discloses deployment traits (self-hosted, dependency-free) and the pre-fill behavior.

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?

Four sentences, with the core purpose front-loaded in the first sentence. Each sentence earns its place: purpose, mechanism, output, and parameter usage. It is slightly verbose in phrasing ('a dead-man's switch,' 'not just alerting on it') but remains dense with useful information and has no wasted clauses.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers the essential ground: what the script does, what the return value is (source plus setup snippet), and how the parameters feed into it. It implies that omitting params yields a generic script. Only minor details like exact return format or setup snippet contents are unstated, and these are not critical for correct invocation.

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 the baseline is 3. The description adds genuine value beyond the schema by explaining how the parameters are used: they optionally pre-fill the returned script (workspace/limit/keys) so it can be dropped straight into the project. This connects inputs to output behavior in a way the schema alone does not.

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?

States a specific verb (Get) and resource (killcord script), then explains exactly what that resource is: a dead-man's switch that polls Anthropic's Admin Usage & Cost API and deactivates the key when spend crosses a limit. The description goes beyond a label to convey mechanism and intent, so an agent knows precisely what it is retrieving.

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 sibling tools exist, so there is nothing to differentiate against, which lowers the bar. The description still supplies clear usage context: it is for stopping a runaway agent loop rather than merely alerting on spend, implying when an agent would want it. It lacks explicit when-not-to-use statements or exclusions, but the use case is unambiguous.

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