append_issue_log

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining that log entries create 'a permanent audit trail' (implying immutability) and that timestamps are 'automatically added by system.' However, it doesn't address important behavioral aspects like whether this operation requires specific permissions, what happens if the issue doesn't exist, whether there are rate limits, or what the response format looks like. The description adds some context but leaves significant gaps for a mutation 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?

While the description is well-structured with clear sections, it's excessively verbose for a tool with only 2 parameters. The detailed lists of 'Log entry purposes,' 'Log content guidelines,' and 'Activity tracking patterns' could be condensed or moved to external documentation. The core functionality could be explained in 2-3 sentences rather than multiple paragraphs, making it less front-loaded than ideal.

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 mutation tool with no annotations and no output schema, the description provides good context about the tool's purpose and usage patterns. However, it lacks critical information about error conditions, authentication requirements, response format, and system constraints. The detailed usage examples partially compensate but don't fully address the gaps in behavioral transparency needed for a write operation.

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 input schema has 100% description coverage, providing clear documentation for both parameters ('ID of the issue to append log to' and 'Contents to append to the log'). The description doesn't add any parameter-specific information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 tool's purpose with a specific verb ('Appends') and resource ('content to an issue's log in the task trellis system'). It distinguishes this tool from siblings like 'create_issue' (creates new issues), 'update_issue' (modifies issue properties), and 'delete_issue' (removes issues) by focusing specifically on adding to an audit trail rather than managing the issue itself.

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 explicit guidance on when to use this tool: 'Use this tool to add progress updates, notes, or activity records to an issue's audit trail.' It also implicitly distinguishes from alternatives by focusing on log appending rather than issue creation, modification, or deletion. The detailed examples of log entry purposes further clarify appropriate use cases.

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