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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states the mutation ('Create a new Trello board') and the return behavior ('Returns: The Trello API response containing the created board details'). It does not mention auth, error cases, or side effects, but for a one-parameter create operation this is sufficient.

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 appropriately sized, front-loaded with the core purpose, and then uses clear Args/Returns sections. Every sentence is necessary and there is no filler or redundancy.

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?

The tool has only one simple required parameter, the description explains it, and an output schema exists for return details. The description is complete enough for an agent to invoke this tool correctly without additional context.

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 contains no property descriptions (0% schema coverage), so the description's Args section adds real value by explaining that 'name' is 'the name to assign to the new board.' It fully clarifies the only parameter, though it does not add constraints like length or format.

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 opens with a specific verb and resource: 'Create a new Trello board.' This clearly distinguishes it from sibling tools like create_list, create_card, delete_board, and search. Even without additional context, an agent can tell exactly what operation this tool performs.

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 implies the tool should be used when creating a Trello board, but it provides no explicit 'when to use' or 'when not to use' guidance. It does not name alternatives or conditions for choosing this tool over a sibling, leaving usage entirely implied.

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

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 only states that it creates a card and returns the API response, but does not mention side effects, error conditions, permissions, or idempotency. This is a significant gap 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?

The description is extremely efficient: a single sentence for the purpose, followed by clear Args and Returns sections. No wasted words, and the main action 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 simple one-parameter tool with an output schema, the description covers the essential input and return behavior. It lacks details on error handling or defaults, but these are not critical for a straightforward creation action.

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 description explicitly explains the idList parameter: 'The Trello list ID where the card will be created.' This adds essential meaning beyond the schema's type-only definition, which is critical since schema description coverage is 0%.

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 states 'Create a new card in a Trello list' with a specific verb (create), resource (card), and location (list). It clearly distinguishes from sibling tools like create_list and delete_card, leaving no ambiguity about what action this tool performs.

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 purpose implies usage (when you want to add a card), but the description does not explicitly mention when to use this tool versus alternatives, nor any exclusions or preconditions. It is adequate but not proactive guidance.

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

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the obvious creation action and the return value, without mentioning prerequisites like an existing board, required permissions, irreversibility, or possible side effects.

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 main action is front-loaded, and the Args section is compact and useful. The Returns section is slightly redundant given an output schema exists, but overall there is no fluff or unnecessary marketing language.

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 simple two-parameter create operation with an output schema, the description covers the purpose, both parameters, and the response shape. It does not discuss prerequisites or authentication, but the low complexity and available structured data make it largely complete.

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 0%, and the description compensates by defining both parameters: name as the name for the list and idBoard as the Trello board ID. It adds meaningful context beyond the bare schema, though it lacks examples or validation detail.

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 states a specific verb ('Create'), a specific resource ('a new list'), and the context ('on a Trello board'). This clearly distinguishes it from sibling tools like create_card and create_board.

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 operation is clearly implied: use this when creating a list on a board. However, it does not explicitly mention when not to use it or point to alternatives such as create_board or create_card, so usage guidance remains implicit rather than explicit.

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

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It states the board is deleted and that a confirmation response is returned, but it does not mention permanence, cascading deletion of lists/cards, or required permissions, all of which are material for a destructive 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?

The description is compact and front-loaded: one clear opening sentence, then a minimal Args/Returns structure. Every element earns its place with no fluff or repetition of the schema.

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 one-parameter delete operation with an output schema, the invocation requirements are adequately covered (id and a confirmation return). However, the absence of deletion-impact context such as irreversibility or what happens to contained cards/lists leaves the definition incomplete for a destructive tool with no annotations.

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 coverage is 0%, so the description must document the single parameter; it does so by explaining that 'id' is 'The Trello board ID to delete.' This adds real meaning beyond the bare title 'Id' in the schema. A 4 is appropriate because the explanation is correct and sufficient, though terse.

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 uses a specific verb-resource pair ('Delete a Trello board'), so an agent can tell this is a destructive board-level operation rather than a card/list operation. It does not add any qualifiers or side-effect scope to further differentiate from sibling tools, so it stops short of a 5.

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 about when to use this tool versus alternatives such as delete_card or create_board, and no conditions, prerequisites, or exclusions are stated. The agent must infer the tool's role entirely from its name and the one-line description.

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

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions 'Returns: The Trello API response confirming the deletion,' but does not state that deletion is permanent, irreversible, or may fail for nonexistent IDs, and it does not mention permission 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 compact and well-structured with a leading sentence, Args block, and Returns block. No redundant text appears; every sentence contributes to understanding the tool.

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 one-parameter mutation tool with an output schema, the description covers the core essentials: action, parameter, and return value. However, it lacks any warning about the destructive/permanent nature of deletion, which would be important for an agent to weigh before 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?

Schema coverage is 0%, so the description must explain the parameter. The line 'id: The Trello card ID to delete' provides clear semantic meaning beyond the schema's bare string type, fully covering the only parameter.

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 opens with 'Delete a Trello card,' a clear verb+resource statement that unambiguously identifies the operation. Among siblings (create_list, create_card, search, create_board, delete_board), this is distinct and self-explanatory.

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 given about when to use this tool versus alternatives. It does not state prerequisites, such as needing an existing card ID, nor does it distinguish itself from delete_board or other destructive tools.

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

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

With no annotations, the description must carry the burden of behavioral disclosure. It states the return value and implies read-only search, but it does not explicitly confirm no side effects, rate limits, or failure behavior.

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 dense and well-structured: purpose first, then Args, then Returns. There is no filler or redundant background.

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 simple search tool with an output schema present, the description covers the purpose, parameters, and return value. Minor omissions like authentication or rate limiting are not critical 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?

The schema lacks property descriptions, but the description provides meaningful explanations for all three parameters: query is the search text, and the limit parameters cap the returned cards/boards. This fully compensates for the 0% schema coverage.

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 first sentence identifies a specific action (search by text) and resource (Trello cards and boards), making the tool's function immediately clear. This also separates it from the sibling create/delete tools.

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 intended use is clear: find cards/boards by text. It does not explicitly state when not to use it, but there are no alternative search siblings requiring exclusion, so the context is sufficient.

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