project_status

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

Disclosed what the tool returns (stats, health, tool list, queue, tips). No annotations provided, so description carries burden; it adequately describes behavior as a read-only status snapshot.

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?

Well-structured with bullet points; front-loaded main purpose. Slightly lengthy but every sentence adds value. Could be more concise, but still effective.

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 annotations and presence of output schema, description is sufficiently complete for a status tool. It covers key aspects without gaps.

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?

Zero parameters; schema coverage 100%. Description adds no param info, but baseline for 0 params is 4, and no further meaning is needed.

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?

Clear statement of purpose: 'Live MidOS system status + quick-start guide for your agent.' Lists specific components returned. Differentiates from sibling tools by focusing on overall orientation rather than specific actions.

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 'Call this anytime' and advises to 'Use it to orient yourself and teach your agent how to leverage MidOS.' Lacks explicit when-not-to-use, but context is clear for a status command.

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