telos.mcp.freshness

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

Discloses read-only, zero-auth, no external side effects. Also describes return format (JSON with MATCH, DRIFT, UNVERIFIABLE). No annotations provided, so description carries full burden and does so thoroughly.

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 sentences with no wasted words. Front-loaded with use case, followed by behavioral traits and output. Extremely efficient.

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?

Given no parameters and no output schema, description covers purpose, usage, behavior, and output states. Missing details on potential errors or edge cases, but sufficient for a simple read-only check.

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?

No parameters in schema, so description naturally cannot add parameter details. Baseline for 0 parameters is 4; description is consistent and does not miss anything.

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 the tool's function: comparing loaded MCP servers against expected versions, tools, and probes. The verb 'compare' and specific resource 'freshness' make the purpose explicit and distinct from sibling tools.

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 says 'Use when a host must compare...', providing clear context. Does not mention when not to use or suggest alternatives, but the context is sufficient for an agent to decide.

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