Portal Help Tickets

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

No annotations are provided, so the description carries full burden. It only notes the login requirement, but does not disclose read-only nature, output details, or other behaviors (e.g., pagination, filtering). This is insufficient for a tool with no annotations.

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 with no unnecessary words. However, it is quite brief for a tool with no annotations; slightly more context (e.g., what the output looks like) would improve completeness without sacrificing conciseness.

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 0 parameters and an output schema that the agent can access, the description does not need to explain return values. However, the tool has no annotations, so the description should provide more behavioral context. The login requirement is mentioned, but overall it feels minimal for a tool with no structured metadata.

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 0 parameters, and schema description coverage is 100% (vacuously). The description does not need to add any parameter details, as there are none. The requirement 'requires login' is an environmental condition, not a 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 clearly states the tool reads help desk tickets from the İTÜ Portal. The verb 'Read' and resource 'help desk tickets' are specific and unambiguous. Among many sibling tools, none are related to help tickets, so it is well-distinguished.

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 mentions 'requires login' but does not specify when to use this tool versus alternatives or when not to use it. It implies usage for reading tickets, but no explicit guidance or exclusions are provided. Sibling tools do not cover help tickets, so no alternative is stated.

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