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

With no annotations, the description carries the full behavioral burden. It does disclose one trait ('value discarded'), suggesting the input is not retained, but it does not state what is returned, whether this is a pure syntax check, what happens for non-matching values, or whether any side effects exist.

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 under-specified rather than usefully concise. It is a short fragment with no sentence structure and does not provide enough information for the length to be an asset.

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 tool with 9 optional parameters, no output schema, no annotations, and many similar sibling tools, this description is far too incomplete. An agent cannot determine what ISWC T-shape means, which parameter is relevant, or what the tool returns.

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 100%, so the parameters are already documented in the schema. The tool description adds no parameter-specific detail beyond the redundant 'value discarded' phrase, so the baseline of 3 applies.

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 is a fragment that essentially restates the tool name: 'ISWC T- shape' does not explain that the tool validates or checks an ISWC value, and there is no explicit verb or resource. It adds a small detail ('T- shape') but leaves an agent to infer that this is a shape-check operation.

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 about when to use this tool versus siblings like jira-key-shape, domain-shape, or wiki-title-ok. No mention of alternatives, exclusions, or the intended context for an ISWC shape check.

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