Start planning a day

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

No annotations provided, so description carries full burden. It discloses that the tool returns a planning brief, date, existing plan, objectives, and carry-over feed. No mention of side effects, but for a read-like operation this is sufficient; could be improved by noting any 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?

Three sentences, efficient and front-loaded with 'START HERE'. Every sentence adds value, though the enumeration of returned items could be formatted more concisely.

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 fully explains what the tool returns. The single optional parameter is well-documented. The tool is straightforward and the description covers all necessary context for correct invocation.

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?

Only one optional parameter 'date' with schema description 'YYYY-MM-DD; default today'. Schema coverage is 100%, so baseline 3. Tool description does not add additional meaning beyond the schema; however, the context of date is implied by the tool's purpose.

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?

Clearly states it is the starting point for planning a day and enumerates the returned information (brief, date, plan, objectives, carry-over). Differentiates among siblings by indicating 'START HERE' and naming 'save_plan' as the next step.

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 'START HERE' to indicate when to use, and directs 'Follow the brief, then save_plan' for subsequent action. Implicitly excludes other siblings by positioning itself as the entry point, though does not explicitly list when not to use.

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