project_status

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

Discloses that setting ensure_running=true launches Resolve, a side effect. No annotations exist, so the description carries the burden. It lacks mention of error or fallback behavior, but overall is transparent for a simple reading tool.

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 concise sentences, with the most important information first (what it reports), followed by usage advice. No extraneous words.

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 output schema, the description lists all reported items (version, page, database, project, timeline) adequately. It also provides session-start guidance, making it complete for its purpose.

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?

The description adds meaning to the sole parameter ensure_running beyond the schema's type and default, explaining its purpose to launch Resolve if not running. This fully compensates for the schema coverage gap.

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 uses specific verb 'Report' and lists exact resources: version, current page, database, open project, and timeline. This clearly distinguishes it from sibling tools like project_open or timeline_create.

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 recommends calling this first in a session to check state, and explains when to set ensure_running=true. This provides clear when-to-use guidance without needing alternatives.

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