all the tools

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the tool exports data (read-only operation), includes metadata/tasks/dependencies hierarchically, requires project ID, has fixed JSON format for V1, and returns a JSON string. However, it doesn't mention potential size limitations, error conditions, or authentication requirements.

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?

The description is perfectly concise with four focused sentences that each add value: first states the core purpose, second details what's included, third mentions the required parameter, fourth specifies the return format. No wasted words, and the most important information (what the tool does) is front-loaded.

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 2-parameter tool with no annotations and no output schema, the description provides good coverage: it explains what data is exported, the required parameter, format constraints, and return type. The main gap is lack of output schema, but the description compensates by specifying the return is a 'JSON string representing the project data.' Could be more complete with error handling or size considerations.

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 100%, so the schema already fully documents both parameters. The description adds minimal value beyond the schema - it mentions the required project ID and that format is fixed to JSON, but doesn't provide additional semantic context about parameter usage or constraints beyond what's in the schema descriptions.

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?

The description clearly states the specific action ('Exports'), resource ('complete data set for a specified project'), and output format ('as a JSON string'). It distinguishes from siblings like importProject (opposite direction) and listTasks/showTask (partial views) by emphasizing completeness and hierarchical structure.

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?

The description provides clear context for when to use this tool ('to export complete project data') and mentions the required project ID. However, it doesn't explicitly state when NOT to use it or name specific alternatives like listTasks for partial data, though the distinction is implied through the emphasis on completeness.

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