basecamp_get_schedule_entry

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get', indicating a read operation, but gives no information about return format, error behavior, authentication needs, or any side effects. The description is too sparse to meaningfully convey behavioral context.

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 concise sentence, which is suitably front-loaded and free of fluff. However, it is under-specified, making it more a placeholder than informative content; thus it earns a mid-range score.

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 a simple read-by-ID signature, but with no annotations and no output schema, the description should clarify what the returned schedule entry looks like or any relevant contextual details. The one-sentence description leaves the agent without enough information to confidently use the 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 0%, and the description does not mention the required parameters (entry_id and project_id) or explain their semantics. The description adds no value beyond the bare schema, and with no parameter explanation, an agent would lack guidance on what values to provide.

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 verb 'Get' and the resource 'schedule entry/event', which distinguishes it from sibling tools like list, create, and update schedule entries. It communicates the core purpose of retrieving a single specific schedule entry, though it could be more explicit that it fetches by ID.

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 usage for retrieving a single schedule entry, contrasting with sibling listing tools, but it does not explicitly state when to use this over alternatives or any prerequisites. The context is clear for a simple get operation, but no direct exclusions or alternative references are provided.

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