get_component_demo_run

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

With no annotations, the description carries the full burden and does add real behavioral value: it declares the call is non-mutating in effect (no queueing, no retries, no second billing) and warns that result-validation context is in-memory and lost on server restart, which is a non-obvious and consequential constraint. It leaves unexplained whether the call blocks until completion or returns a pending status, and how a missing/expired run_id is reported.

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?

Three short sentences, each carrying distinct information: what is returned, what side effects do not occur, and a durability caveat. The identifying scope ("already queued") is front-loaded with no filler.

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 single-parameter read tool with no output schema, the description covers the essentials: it names the two return states (status vs. completed result), rules out side effects, and flags the restart limitation. Minor gaps are the enumeration of status values and the not-found case, which matter little given the tool's simplicity.

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 0% for the single run_id parameter, so the description must compensate; it does imply the id is a handle issued by this process's earlier queueing call, but gives no format, expected pattern, or behavior for stale ids. That is partial compensation for a required, undocumented parameter.

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?

Uses a specific verb+resource pair ("Retrieve status or the completed result for an Agent inspection") and scopes it with "already queued by this ComponentPilot process," which implicitly separates it from the queueing sibling inspect_component_demo. It stops short of naming that sibling, so the distinction requires an inference from the word "already queued."

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?

"already queued" plus "never queues, retries, or bills a second Agent execution" tells the agent this is a follow-up/polling call, not a way to start work. However, no alternative is named explicitly and there is no statement of what to do when run_id is unknown or expired, so usage is implied rather than prescribed.

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