get_someday

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions the API used and the action, but does not indicate whether the operation is read-only, what side effects exist, or what the return payload contains beyond 'Someday tasks'. This is a basic getter, but the lack of any side-effect or safety hint leaves the agent without important context.

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 a single, concise sentence with no fluff. It is front-loaded with the action and resource, and every word adds value. It is appropriately short for a tool with no parameters.

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?

Despite having an output schema, the description does not disclose any operational details such as read-only nature, performance considerations, or any prerequisites. Without annotations, an agent cannot tell if this is safe to call in any context or if it requires certain permissions. The description is minimal and leaves the agent with unanswered questions about when and how to use it.

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?

There are no parameters (schema is empty, coverage 100%), and the baseline for 0 params is 4. The description adds a bit of meaning by specifying the resource ('Someday tasks'), which helps interpret the output schema. No further compensation 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?

The description clearly states the action ('Get') and the resource ('Someday tasks'), naming the specific list from Things. It is distinguishable from sibling tools by the explicit 'Someday' qualifier, though it does not elaborate on what 'Someday' means or how it differs from 'Anytime' or 'Upcoming'.

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?

There is no guidance on when to use this tool versus its siblings (e.g., get_today, get_anytime). The description only states what it does, leaving the agent to infer the appropriate context based on the tool name. No when-not-to-use or alternative routing is provided.

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