fee_schedule_get

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

No annotations are supplied, so the description carries the full burden. It does disclose a useful behavioral detail — that the response includes a freshness state with three enumerated values — but says nothing about read-only semantics, authorization, or what a STALE or NO_SCHEDULE result means for the caller. For a tool with zero annotation coverage, that is a substantial gap.

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?

A single compact sentence, which is good, but the leading 'T0.' token is unexplained noise that consumes attention without conveying anything the agent can act on. The key content is front-loaded, so it is structurally acceptable rather than well-crafted.

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?

With no output schema, no annotations, and 0% parameter documentation, the description is the only source of truth and it covers little. It does not explain how the freshness state should influence the agent's next action, nor what as_of does, which are the two things an agent most needs to call this correctly.

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% for two parameters. The description implies 'venue' but never explains it, and the optional 'as_of' parameter — clearly the most semantically loaded one, since it presumably selects a historical schedule — is completely unmentioned. The description does not compensate for the schema gap.

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?

States a concrete resource (the venue's current fee schedule) and what accompanies it (a freshness state with named enum values FRESH | STALE | NO_SCHEDULE). An agent can tell this apart from fee_schedule_register, which presumably writes a schedule. The 'T0.' prefix is unexplained and adds no clarity.

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 when-to-use guidance, no statement of when to prefer this over fee_schedule_register or venue_status, and no explanation of when the optional as_of should be supplied. The word 'current' hints at a point-in-time read but the agent must infer everything else.

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