log_to_notion

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

No annotations are present, so the description carries full burden. It does not disclose behavioral traits such as that it is a write operation, requires authentication, or how it handles duplicates. 'Full details' is vague.

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 sentence, which is concise. For a tool with 8 parameters, it could be slightly longer but is not overly verbose.

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 the tool has 8 parameters, 4 required, no output schema, and no annotations, the description is insufficient. It does not explain return values, error handling, or the need for prior setup (sibling 'setup_notion_db' hints at this).

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?

With 63% schema description coverage, the description adds no meaning beyond the schema. It does not explain how parameters map to the Notion database fields or that it inserts a new row. The phrase 'full details' does not compensate.

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 'Log a job application to the Notion Job Tracker database with full details' clearly specifies the verb (log) and the resource (job application to Notion database). It is distinct from sibling 'update_application_status' which implies modifying existing records, though it could explicitly state that it creates a new entry.

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?

No guidance is provided on when to use this tool versus alternatives like 'update_application_status'. The description lacks any context about prerequisites or scenarios for use.

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