eds_get_status

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

Describes a read operation without side effects, but lacks disclosure of any potential restrictions, rate limits, or authentication needs. Since no annotations are provided, the description bears full burden and is minimally adequate.

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?

Single sentence, front-loaded with essential information, no extraneous words. Highly concise.

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 simple tool with one parameter and no output schema, the description sufficiently covers what the tool returns. However, it does not explain the meaning of 'preview, live, code-bus' status, which may be domain-specific but not critical.

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% with one parameter described; the description adds little beyond what the parameter description already provides ('Resource path to check status for'). Baseline at 3.

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 clearly states verb 'Get', the resource 'preview, live, and code-bus status for an EDS resource', and includes specifics (URLs and modification timestamps). It distinguishes from sibling tools that focus on other actions like bulk preview or publishing.

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?

Implies usage when status information is needed, but no explicit guidance on when to use this tool vs alternatives among siblings (e.g., eds_get_page for page content). No exclusions or context provided.

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