Show Time And Material Notification

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. The description adds value by noting that the response is a paginated JSON array with pagination metadata, which is not captured in annotations. No contradiction.

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 concise at four sentences, front-loading the purpose and usage. Each sentence adds value without redundancy. It is well-structured: purpose, usage, pagination details, API reference.

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 low complexity (3 parameters, no output schema) and rich annotations, the description covers purpose, parameter usage, and endpoint info. It lacks explicit error handling or return format details beyond pagination, but is sufficient for a read-only tool.

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 baseline is 3. The description adds meaning beyond the schema by explaining how page and per_page control pagination and that the response includes pagination metadata, helping the agent understand the parameters' behavior.

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 'Return Time And Material Notification detailed information' and specifies it fetches full details of a specific Field Productivity record by identifier. It distinguishes itself from sibling tools like create_a_new_time_and_material_notification, show_time_and_material_entry, and list_all_time_and_material_entry by focusing on a specific resource and 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?

The description explains when to use it: 'fetch the full details of a specific Field Productivity records by its identifier.' It also provides pagination guidance. However, it does not explicitly state when not to use it or mention alternatives, which would have improved the score.

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