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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's real contribution is the deprecation lifecycle — that behaviour is time-boxed and will break after 2026-11-10 — which is genuinely useful context not in the annotations. It says nothing about what the feed returns or how the migration maps fields.

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?

One short sentence with the deprecation status front-loaded ahead of the remedy, which is the right ordering for an agent deciding whether to call it. The only waste is the cryptic 'with space' clause that costs more parsing than it saves.

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 deprecated tool the minimum an agent needs is 'do not use, migrate here with this argument', and that is delivered. But with no output schema, 0% parameter coverage, and no migration mapping, an agent that must still call it until the sunset date has no idea what the five inputs mean or what comes back.

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?

Five parameters (q, tag, limit, space, before) with 0% schema description coverage and no enums, so the description carries the full documentation burden. It only alludes to 'space', and only in the context of the replacement tool — q, tag, limit and before are completely undocumented in both places.

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 never states what trana_feed does — no verb, no resource, no data domain. It is purely a deprecation banner plus a pointer at node_list. An agent learns nothing about the operation itself, only that it should be avoided, which is closer to a tombstone than a purpose statement.

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?

Explicitly names the sunset date (2026-11-10) and the replacement (node_list with space), which is exactly the when-not-to-use / use-instead guidance agents need. The phrase 'with space' is terse and leaves the agent to infer that it means the space parameter of node_list, so it stops short of a 5.

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